Repository navigation
chore: sync main to published release 2.5.0 - #42
Merged
Merged
Conversation
Knucklessg1
enabled auto-merge (squash)
November 16, 2026 16:02
Main carried 2.3.10 while 2.5.0 is the newest release on the package index. Set the project version to 2.5.0 in pyproject.toml and uv.lock. No tag is created. Spec: none (sync main to the published release version) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Knucklessg1
force-pushed
the
chore/version-sync-20261116
branch
from
November 16, 2026 16:11
ad0e6d2 to
19628a3
Compare
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.
Main carried 2.3.10 while 2.5.0 is the newest published release. This sets the project version in pyproject.toml and uv.lock to 2.5.0 so release drift no longer reports it. No tag is created.
🤖 Generated with Claude Code