chore(deps): move build off the yanked 1.5.1 release - #1087
Merged
Conversation
PyPI yanked build 1.5.1 ("Considers breaking changes, will discuss
re-releasing as a new major version"). Re-lock at 1.5.0, the latest
non-yanked release, so fresh syncs stop installing a yanked version
and uv stops warning on every lock operation.
Co-Authored-By: Claude Fable 5 <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.
Summary
Follow-up to #1086.
uv.lockpinsbuild==1.5.1, which PyPI has yanked (reason: "Considers breaking changes, will discuss re-releasing as a new major version"). Everyuv lockoperation warns about it, and fresh environments install a yanked release.This re-locks
buildat 1.5.0, the latest non-yanked release.buildis a dev-group tool only (dev = ["build>=1.2.0", ...]); nothing shipped depends on it.uv lock --checkpasses; the diff is the three lock lines for thebuildentry.Test plan
🤖 Generated with Claude Code