Repository navigation
ci(release): adopt CHANGELOG.md pattern with generated release notes - #72
Merged
Merged
Conversation
Add generate-notes.sh (conventional-commit grouping, breaking-change detection from PR labels/body) and update-changelog.sh, shared with the other repos. release.yml now generates the notes from the previous release, publishes them as the GitHub Release body, and commits the CHANGELOG.md entry to main. Backfill CHANGELOG.md for v0.2.0–v0.3.13. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Bring the release flow in line with the shared pattern used across the other repos: a committed
CHANGELOG.mdand GitHub Release notes generated from conventional commits, grouped by type..github/scripts/generate-notes.sh— groups commits between two release tags into Features / Bug Fixes / Refactoring / Documentation / CI / Maintenance, bolds scopes, capitalizes descriptions, and leads with ⚠ BREAKING CHANGES detected from a!marker, aBREAKING CHANGE:footer, or the merged PR'sbreaking-changelabel/body. Version-bump and digest-pin commits are filtered as release noise..github/scripts/update-changelog.sh— inserts the entry at the top ofCHANGELOG.md(or replaces an[Unreleased]section).release.yml— after the tag force-moves: resolve the previous release from the release list (the pin commit is off main, so git can't discover it), generate notes,gh release create --title --notes-file, then check out main and commitdocs: update CHANGELOG.md for <tag>. Job gainspull-requests: readfor the PR lookups.CHANGELOG.mdbackfilled for v0.2.0–v0.3.13 from the existing tags and release dates.Test plan
generate-notes.sh v0.3.13 v0.3.12→ only feat: surface priority-doc skips and token budget in job summary #70;v0.3.9 v0.3.8→ fix: drop false maxScanBytes justification in priorityDocsInContext comment #57 + fix: replace SDK AbortSignal.timeout with application-level AbortController #58, pin/release commits absentCHANGELOG.mdentry committed to main🤖 Generated with Claude Code