Repository navigation
chore: release 3.0.0 - #237
Merged
Merged
Conversation
Version bump for the stable release; the release itself is published only after the candidate passes the release gates. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The version in
version.txtis set to3.0.0for the stable release. Nothing else changes; the game's pin of its kit is left as it is.Opened by release automation. Nothing is published by this PR: once it is merged, the merge commit must pass every CI check and a save-format check and a save-compatibility check against
2.1.0, and only a commit that passes is tagged3.0.0. See python-release-gates.drafted by Claude on behalf of Daniel Stephenson