vatsrahul1001 opened a new pull request, #71162:
URL: https://github.com/apache/airflow/pull/71162
The release constraints resolution (`generate_constraints_pypi_providers`)
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 (`pypi-providers-only`, which
skips building providers into `dist`) cannot satisfy them and the `Release
constraints` workflow fails with `No solution found`:
```
× No solution found: there are no versions of
apache-airflow-providers-ibm-mq,
and apache-airflow[all]==3.3.0 depends on
apache-airflow-providers-ibm-mq>=0.1.0
```
This installs the `not-ready` providers from local source (mirroring the
existing `./airflow-ctl` path install) so the resolution stays solvable. `pip
freeze` renders a path install as a `... @ file://...` line, which
`freeze_distributions_to_file` already drops, so a not-ready provider is never
pinned in the released constraints file.
`not-ready` is 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 into `dist`, 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?
- [X] Yes — Claude Code (Opus 4.8)
Generated-by: Claude Code (Opus 4.8) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
