Auto-generate release notes in release.sh#130
Merged
Conversation
The release workflow hardcoded --notes="Release vX", so automated releases (e.g. v0.5.1) shipped with no changelog. Switch to gh release create --generate-notes so GitHub produces the "What's Changed" + Full Changelog section from merged PRs. CLI binary assets are unchanged.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Auto-approved: Updates release script to auto-generate changelog from merged PRs. Low-impact, isolated change to release process.
Re-trigger cubic
This was referenced Jul 9, 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
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.
Automated releases hardcoded
--notes="Release v${VERSION}", so they shipped with no changelog (e.g. v0.5.1 has no "What's Changed", unlike the manually-published v0.5.0).Switch the release step to:
--generate-notesmakes GitHub build the What's Changed + Full Changelog section from merged PRs automatically, on every future release. CLI binary assets are unchanged.Should be merged before tagging the next release so that release picks it up (the workflow runs
release.shfrom the tagged commit).Verified
bash -n cicd/release.shparses.Summary by cubic
Use
gh release create --generate-notesincicd/release.shand set--title "v${VERSION}"so releases auto-include What's Changed and Full Changelog from merged PRs. Fixes missing changelogs in automated releases; CLI assets unchanged; merge before next tag.Written for commit 081573f. Summary will update on new commits.