feat(release-train): span stable release notes from the previous stable release#10
Merged
Merged
Conversation
…le release Stable graduations produced nearly-empty GitHub Release notes because the work was attributed to the alpha/beta changelog entries and --unreleased only covered the merge commits since the last beta tag. Stable releases now generate their notes over <previous-stable>..HEAD with pre-release tags ignored, yielding one flat section that describes everything landing in production. Pre-releases keep the previous behavior. https://claude.ai/code/session_01MFD8imoXtKUEUoZTvL5Ztv
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.
Problem
Stable graduations produced nearly-empty GitHub Release notes (see gardenia-api
v0.16.0): the actual work was attributed to the alpha/beta changelog entries, and--unreleasedonly covered the merge/chore commits since the last beta tag.Change
For stable releases, the release body fragment is now generated over the range
<previous-stable>..HEADwith pre-release tags ignored (--ignore-tags '.*-(alpha|beta|rc).*'), producing one flat section that lists everything actually landing in production. Pre-releases keep the previous--unreleasedbehavior, and the full-historyCHANGELOG.mdgeneration is untouched.The regex is single-quoted inside the step output because
git-cliff-actionsplices itsargsinput directly into a bash command line.Verification
Ran the exact command locally against the real gardenia-api repo state simulating the
v0.16.0graduation — output is a single[0.16.0]section containing the 2 features, 3 fixes and tests that flowed through0.16.0-alpha.0/0.16.0-beta.0sincev0.15.2, instead of the empty body that release shipped with. Detect test suite still passes (36/36).https://claude.ai/code/session_01MFD8imoXtKUEUoZTvL5Ztv
Generated by Claude Code