[codex] Add release note bodies - #18
Merged
Merged
Conversation
Generate GitHub release notes with install steps, artifact checksums, and grouped changelog entries so tagged releases publish useful bodies.
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
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
scripts/write-release-notes.shto generate tagged release bodies with install instructions, Arrowhead highlights, artifact checksums, grouped conventional-commit changelog entries, and a full compare link.release-notes.md, and publish it viasoftprops/action-gh-releasebody_path.arrowheaddbinary.Why
Arrowhead releases previously uploaded artifacts without the richer release body already used in
tp7cli. This keeps the tag-driven release output useful for users installing from Homebrew or downloading macOS archives directly.Verification
bash -n scripts/write-release-notes.shv0.11.0YAML.load_filecargo fmt --allcargo check --all-targetscargo clippy --all-targets -- -D warningscargo test --all-targets -- --nocaptureactionlintwas not installed locally, so it was not run.