chore: sync uv.lock to package version 2.1.0#8
Merged
Conversation
semantic-release bumps the version in pyproject.toml but does not run `uv lock`, so the lockfile's own-package entry lagged at 2.0.0. Every `uv run` then re-stamped it, producing spurious working-tree drift. Re-resolve (cache hit, single-line change) to align it. Co-Authored-By: Claude Opus 4.8 (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
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.
Why
semantic-releasebumps the version inpyproject.toml(now2.1.0) but does not runuv lock, so the lockfile's own-package entry stayed at2.0.0. Everyuv runthen re-stamped it to2.1.0, producing spurious uncommitted working-tree drift.What
Ran
uv lockto align it. Single-line change, no transitive churn (full graph resolved from cache):Release impact
Typed
chore:, so semantic-release will not cut a new version on merge (per.releaserc.json).Follow-up (optional)
To stop this recurring on every future release, add a
uv lockstep to.releaserc.json's prepare phase (alongside the existingsedversion bump) so the lockfile is updated and committed as part of each release.🤖 Generated with Claude Code