fix: handle missing module release tags - #112
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.
修复
module-publish在标签不存在时的判断：gh api的 404 会把错误 JSON 写到标准输出，原来的|| true将它误判成已有标签，导致 npm 已发布后流程失败。现在依据命令退出状态清空existing。同时记录平台正式版与首包发布结果，并修正升级文档中的 CLI 版本命令。
验证：YAML 解析通过；首包
activity-log@0.2.1已在公共 registry 可读，其v0.2.1标签和 Release 已补到发布提交。