Repository navigation
ci: keep uv.lock in step with the version bump - #7
Merged
Merged
Conversation
The release bumped pyproject.toml but not uv.lock, so uv sync in the next release rewrote the lockfile and git pull --rebase refused to run on the dirty tree (the 0.2.1 release failed this way). The bump now relocks and commits uv.lock with pyproject.toml, and the pull autostashes.
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 release after #5 failed at
git pull --rebase(cannot pull with rebase: You have unstaged changes): the workflow bumpspyproject.tomlbut notuv.lock, souv syncrewrote the lockfile in the runner. The bump step now runsuv lock, commitsuv.lockwithpyproject.toml, and pulls with--autostash. Nothing was tagged or published by the failed run.