Repository navigation
fix(ci): render the GitHub release notes in the release step - #598
Merged
Merged
Conversation
/tmp/release-notes.md was gone when 'Create GitHub release' ran, on both v7.0.0 and v7.0.1, and no step in the workflow deletes it. The step now renders the notes itself with the same script into $RUNNER_TEMP, so the release no longer depends on a file written ten minutes earlier. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RSop9MyLof8XxLTkFnF4KG
|
Docker image built, scanned, and smoke-tested in CI. The PR image is local to this run and is not published. |
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.
Create GitHub releasefailed on v7.0.0 and v7.0.1 with/tmp/release-notes.md is missing or empty. No step in publish.yml deletes the file, and a local canary run did not reproduce it, so the root cause is still unknown.The release step now renders the notes itself with
scripts/changelog-section.mjsinto$RUNNER_TEMP, right beforegh release create. The pre-publish check and the published notes still come from the same script.Checked: the render logic against the 7.0.1 CHANGELOG (1129 bytes);
publish-workflowtests, 21 pass.🤖 Generated with Claude Code