Require uv-dynamic-versioning>=0.8.0 for fallback-version support#1005
Merged
Conversation
Kludex
enabled auto-merge (squash)
June 1, 2026 11:51
Merging this PR will not alter performance
Comparing 
Footnotes
|
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.
The
fallback-versionsetting added in #1003 only works withuv-dynamic-versioning>=0.8.0; 0.7.0's config schema has nofallback_versionfield, so constrained/offline no-git builds could resolve 0.7.x, ignore the key, and fail with the same VCS error.Bumps the
build-system.requireslower bound to>=0.8.0in bothhttpx2andhttpcore2pyprojects.Addresses #1003 (comment).
AI Disclaimer
This PR was developed with the assistance of either Claude or Codex. I've reviewed and verified the changes.