[codex] Use generated release notes placeholder#501
Merged
Conversation
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.
What changed
The app release workflow now seeds draft GitHub releases with
<!-- generated-by-yaak-releases -->instead of a placeholder changelog link.Why
The website release tooling only replaces GitHub release bodies that are empty or already marked as generated. The previous changelog link looked like manual release notes, so
release_ship_betapreserved it and skipped the generated notes update.Impact
Future beta and stable release shipping can replace the draft release body with the website-formatted generated notes.
Validation
git diff --check -- .github/workflows/release-app.ymlNo tags were created or changed.