Repository navigation
docs: curate the release notes before publishing them - #184
Merged
Merged
Conversation
The generated change list repeats one feature across the commits that built it, lists fixes to code no release had, and mixes internal work with what an admin notices. The rc1 range generates 110 entries. The release-notes skill turns that list into the published notes: it sorts every entry into kept, merged, or dropped as unreleased or internal, rewrites the kept ones in one voice, adds Highlights and the upgrade steps, and keeps an audit so no entry is lost. The release gate in dev.md names it as the step before tagging.
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.
Summary
script/release-noteslists one feature once per commit that built it, fixes to code no release had, and internal work. The rc1 range generates 110 entries.release-notesskill: it sorts every generated entry (keep, merge, drop as unreleased or internal), rewrites the kept ones in one voice, writes Highlights and Upgrading, and audits every entry. The release gate indocs/agent/dev.mdnames it as the step before tagging.