You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bin/release ignores changes/ fragments and renames a published heading #682
When package.json's version is already on npm and the only new entries are in changes/, bin/release does not collect the fragments. It raises the version and renames the top heading, which is the published release's.
Seen on 2026-11-21: #679 left changes/fix-family-install-retry.md. bin/release opened #680, which renamed ## 0.125.2 (tag v0.125.2) to ## 0.125.3. Only the changelog guard stopped it. The fragment went out by hand in #681, as 0.125.0 (#673) did.
Expected: bin/release folds changes/*.md into the new version's section, picks patch or minor from the headings, and deletes the fragments, as cli-core's does.
Activity