Build not-ready providers from source when generating PyPI constraints - #71162
Closed
vatsrahul1001 wants to merge 1 commit into
Closed
Build not-ready providers from source when generating PyPI constraints#71162vatsrahul1001 wants to merge 1 commit into
vatsrahul1001 wants to merge 1 commit into
Conversation
The release constraints resolution installs apache-airflow[all], which depends on every non-suspended provider. not-ready providers (currently ibm.mq and common.dataquality) are never published to PyPI, so the PyPI-only release path cannot satisfy them and fails with "No solution found". Install them from local source so the resolution stays solvable; pip freeze renders a path install as a file:// line that is already dropped from the constraints file, so a not-ready provider is never pinned in released constraints.
vatsrahul1001
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
August 5, 2026 08:51
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
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 release constraints resolution (
generate_constraints_pypi_providers) installsapache-airflow[all], which depends on every non-suspended provider.not-readyproviders — currentlyibm.mqandcommon.dataquality— are never published to PyPI, so the PyPI-only release path (pypi-providers-only, which skips building providers intodist) cannot satisfy them and theRelease constraintsworkflow fails withNo solution found:This installs the
not-readyproviders from local source (mirroring the existing./airflow-ctlpath install) so the resolution stays solvable.pip freezerenders a path install as a... @ file://...line, whichfreeze_distributions_to_filealready drops, so a not-ready provider is never pinned in the released constraints file.not-readyis exactly the set of providers that[all]requires (it is generated from all non-suspended providers) but that are absent from PyPI — suspended providers are already excluded from[all]. Their only extra deps (asgiref,common-compat,apache-airflow) are already core/ready, so nothing new is pinned. In the normal CI path the not-ready providers are already built intodist, so this is a no-op there.This currently blocks the 3.3.1 release-constraints run.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines