[v3-3-test] Resolve release constraints against PyPI providers only (#71140) - #71143
Merged
Conversation
A release pins the providers as published on PyPI. Building them from the sources first puts a locally built wheel where the resolution can find it, and anything answered locally is then left out of the constraints - dropping the very pin the release needed. It also makes the release depend on the provider build toolchain working, which is what broke 3.3.1rc1: flit removed --no-setup-py and package preparation failed before any resolution ran. (cherry picked from commit c37ba12)
vatsrahul1001
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
August 5, 2026 04:15
vatsrahul1001
added
the
changelog:skip
amoghrajesh
approved these changes
Aug 5, 2026
potiuk
approved these changes
Aug 5, 2026
vatsrahul1001
added a commit
that referenced
this pull request
Aug 5, 2026
) A release pins the providers as published on PyPI. Building them from the sources first puts a locally built wheel where the resolution can find it, and anything answered locally is then left out of the constraints - dropping the very pin the release needed. It also makes the release depend on the provider build toolchain working, which is what broke 3.3.1rc1: flit removed --no-setup-py and package preparation failed before any resolution ran. (cherry picked from commit c37ba12) Co-authored-by: Jarek Potiuk <jarek@potiuk.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
3 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.
Backport of #71140 to
v3-3-test. Cleangit cherry-pick -x.Makes the release constraints flow resolve providers as published on PyPI rather than building them from the checkout: adds a
pypi-providers-onlyinput (defaultfalse) thatrelease-constraints.ymlsets totrue, gating off the source-providers constraints and the source provider build. This fixes a real correctness bug (a locally-built provider wheel could answer the resolution and then be excluded from the shipped constraints — dropping the very provider a release needs pinned) and unblocks the 3.3.1rc1 constraints run, which died inprepare-provider-distributionsafter flit removed--no-setup-py.Needed on this branch so the 3.3.1 RC-constraints workflow can complete.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines — clean cherry-pick backport of #71140.