ci: align release changelog with template-repo format#13
Conversation
Restructure the changelog generation step to match template-repo's pattern: initialize CHANGELOG outside the PREVIOUS_TAG check, add status messages, and move GITHUB_TOKEN env to step-level. Remove unnecessary sed whitespace stripping and add step id for consistency. The gh API generate-notes call produces "## What's Changed" with merged PR links and a "Full Changelog" comparison URL. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Gemini AI Code ReviewIssues (if any)(none) Previous Issues (for incremental reviews)(none) Suggestions (if any)(none) Notes
Generated by Gemini AI (gemini-3-flash-preview). Supplementary to human reviews. |
Codex AI Code ReviewIssues (if any)(none) Previous Issues (for incremental reviews)(none) Suggestions (if any)(none) Notes
Generated by Codex AI (gpt-5.3-codex). Supplementary to human reviews. |
Review Response Agent (Iteration 1)Status: No changes needed Fixed Issues
Ignored Issues
Deferred to Human
Notes
The agent reviewed feedback but determined no code changes were required. |
Summary
Generate changelogstep to match template-repo's pattern: initializeCHANGELOGvariable outside thePREVIOUS_TAGconditional, check emptiness separately, and add status messagesGITHUB_TOKENenv to step-level (afterrun:block) matching template conventionsedwhitespace stripping from release notes heredocid: release_notesto the release notes step for consistencyThe
gh api repos/.../releases/generate-notescall produces a## What's Changedsection with merged PR links and aFull Changelogcomparison URL, which is appended after the---separator in release notes.Test plan
create_release: trueto verify the release notes include the "What's Changed" sectionhas_changelogoutputGenerated with Claude Code