docs: regenerate changelog for v0.750.0#6509
Open
danielraffel wants to merge 1 commit into
Open
Conversation
Automated by shipyard release-bot hook run after tag push, so CHANGELOG.md and the GitHub Release page stay in sync. Version-Bump: sdk=skip reason="docs-only automated regeneration" Skill-Update: skip skill=ci reason="no workflow shape change" Release: skip reason="bot commit; prevent recursive auto-release"
danielraffel
enabled auto-merge
July 23, 2026 19:24
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.
Automated by shipyard release-bot hook run after tag
v0.750.0— routes the CHANGELOG.md regeneration through a PR so it lands via the merge queue instead of a direct push tomain.