Rename --uv-with to --build-with; reject constraints on unsupported ecosystems - #6116
Merged
Conversation
…cosystems The constraint concept is per-ecosystem, not uv-specific: --build-with now names the generic surface, documented as interpreted per package ecosystem (uvx://: PEP 508 specifiers via 'uv tool install --with'). RuntimeConfig.UVWith becomes BuildWith (wire tag build_with). Also fixes a wart from #6111: a non-empty constraint list on npx:// or go:// builds was silently ignored; createTemplateData now rejects it so users are not left believing an unsupported constraint applied. Flag shipped hours ago and is unreleased, so the rename is free. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
JAORMX
requested review from
ChrisJBurns,
amirejaz,
aponcedeleonch,
blkt,
jhrozek,
rdimitrov and
reyortiz3
as code owners
July 28, 2026 15:57
ChrisJBurns
approved these changes
Jul 28, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6116 +/- ##
=======================================
Coverage 72.40% 72.41%
=======================================
Files 733 733
Lines 75845 75849 +4
=======================================
+ Hits 54918 54927 +9
+ Misses 17034 17031 -3
+ Partials 3893 3891 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
2 participants
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.
Follow-up to #6111, while the flag is hours old and unreleased.
The build-time dependency-constraint concept is per-ecosystem, not uv-specific, so the flag becomes
--build-withonthv runandthv build, documented as "interpreted per package ecosystem" — foruvx://that means PEP 508 specifiers passed touv tool install --with(e.g.--build-with 'mcp<2'). Future ecosystems can map it to their native mechanism (npmoverrides, Go module directives) if/when their builders can support it.RuntimeConfig.UVWith→BuildWith(wire tagbuild_with); swagger and CLI docs regenerated.This also fixes a wart from #6111: a non-empty constraint list on
npx://orgo://builds was silently ignored.createTemplateDatanow rejects it with a clear error, so nobody is left believing an unsupported constraint applied — covered by a new test across both unsupported transports, plus the uvx acceptance case.Lint clean, all touched package tests green, arxiv e2e updated to the new flag name.
🤖 Generated with Claude Code