build: sync uv.lock project version to 0.9.0#18
Merged
Conversation
PSR bumps pyproject [project] version on release but does not touch uv.lock, so after v0.9.0 the lockfile's own package entry lagged at 0.8.1 and `uv sync --locked` (run in CI) would fail. Re-locked to 0.9.0. Co-Authored-By: Claude Opus 4.8 <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
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.
Routine post-release lock sync (same as #15 for 0.8.1).
PSR bumps
pyproject[project].versionon release but does not updateuv.lock. After v0.9.0 the lockfile's own entry lagged at 0.8.1, souv sync --lockedin CI fails.Now that CI is a required status check (branch-protection ruleset), this stale lock blocks all merges until fixed — so this should merge first.
🤖 Generated with Claude Code