fix: separate module npm publish from cross-repo releases - #113
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
主仓的
SFMC_GITHUB_TOKEN可以读模块仓，但在activity-log/afk的 npm 发布完成后，创建模块仓 Git tag 时分别暴露 404 误判和 403 Contents 写权限不足。前者已由 PR #112 修复，后者需要把 npm 发布与跨仓 GitHub 元数据分开。本 PR 增加
create_github_release输入，默认关闭；module-publish成功完成 npm 发布后会提示维护者用有权限的登录态补齐模块仓标签与 Release。具备模块仓 Contents 写权限的 token 配好后可显式打开自动创建。验证：工作流 YAML 解析和
git diff --check通过；已发布的activity-log@0.2.1与afk@0.2.0均已手动补齐对应标签和 Release。