Update release notes workflow and GPT model#779
Merged
Conversation
yaojin3616
marked this pull request as ready for review
July 23, 2026 13:50
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.
What changed
RELEASE_NOTES.mdfrom the release workflow.openai/gpt-4.1toopenai/gpt-5.Why
Align Clawith's release workflow with the CoAligne release flow while keeping release notes available in the release PR and published GitHub Release without modifying a repository-level notes file.
Impact
Automated release PRs now contain only the version-file metadata changes. Published GitHub Releases continue to use the generated notes embedded in the release PR body.
Validation
.github/workflows/release.ymlsuccessfully with Ruby YAML.git diff --check.python3assertion.