fix(release): 浅克隆误打全量 tag + 损坏 changeset 状态 - #74
Merged
Tanya7z merged 1 commit intoJul 25, 2026
Conversation
- tag-packages：CI/--from-existing 只收录已有 name@version；HEAD~1 不可用时禁止全量回退 - extractChangelogNotes：去掉 m 标志，避免 GH Release 笔记被截成首行 - DRY：RELEASE_TAGS_STATE / read-write / packageDirFor；publish 复用 isPreMode - 恢复 pre.json 已消费列表；删除误留的 tame-suns-begin（已发 beta.1，防二次 bump） - changeset-release.yml fetch-depth: 0 Co-authored-by: Shiroha <Tanya7z@users.noreply.github.com>
Tanya7z
marked this pull request as ready for review
July 25, 2026 05:27
Contributor
Author
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
This was referenced Jul 25, 2026
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
2 participants
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.
Summary
审查
main@686bdba（发版编排 + beta.1 发布）后的可验证修复。BLOCKER — LSP / 契约
changeset-releaseCI 默认actions/checkout浅克隆 →HEAD~1失败 →tag-packages旧逻辑回退为「给所有可发包打 tag」，导致未在本轮 publish 的包（sdk/cli/eslint-plugin/qq-bridge/tools）也被推 tag 并创建 GitHub Release。修复：
CI=true/--from-existing：只收录本地已有name@version（changeset publish刚建的 tag）HEAD~1时同样安全回退，禁止全量打 tagfetch-depth: 0双保险BLOCKER — 重复 bump
tame-suns-begin.md在版本已手写 bump 并 publish 为0.2.0-beta.1后仍残留，且pre.json消费列表被截断为仅该 id。下一轮 Version PR 会再次 patch 同一批包。修复： 删除残留 changeset，恢复
pre.json已消费列表；新增fix-release-tag-shallow仅 bump@sfmc-bds/tools。MAJOR — DRY / DIP
RELEASE_TAGS_STATE+ read/write 唯一来源（tag/push/gh）changeset-publish复用isPreMode/ROOTpackageDirFor替代 gh-release 再挖NPM_PUBLISH_PACKAGESMAJOR — GH Release 笔记截断
extractChangelogNotes使用了m标志，$在行尾匹配 → 笔记只剩首行（已发 beta.1 Release 笔记可能已截断）。已去掉m。验证
node --test tools/changeset-release.test.mjsresolvePackagesNeedingTags({})→ 仅 db-server / bds-tools / sfmc 的 beta.1Test plan
tools/changeset-release.test.mjschangeset-release对 pending tools changeset 开 Version PR（不应再二次 bump 已发 beta.1 包）tag-packages日志含[from-existing]，只推真正 publish 的 tag