potiuk opened a new pull request, #71140: URL: https://github.com/apache/airflow/pull/71140
`release-constraints.yml` produces the constraints a release ships, which pin every provider at the version published on PyPI. It was still building the providers from the sources in the checkout first. That is wrong in two ways. The built wheels land in the dist directory that the PyPI resolution reads through `--find-links`, so a locally built wheel can answer for a provider — and `get_locally_build_distribution_specs()` then *excludes* anything answered locally from the constraints file. The provider the release most needed pinned is the one that ends up missing. It is the right behaviour while developing a provider that is not on PyPI yet; it is the opposite of what a release wants. It also makes cutting constraints depend on the provider build toolchain working. That is what broke the 3.3.1rc1 run: `flit` removed `--no-setup-py`, `prepare-provider-distributions` failed on all five Python versions, and generation died before any resolution ran. A new `pypi-providers-only` input on `generate-constraints.yml` (default `false`, so nothing else changes) skips both the source-providers constraints and the provider distribution build. `release-constraints.yml` sets it. Combined with the `generate-no-providers-constraints: "false"` already there, a release run now generates only the PyPI constraints. The airflow and task-sdk distributions are still built — a release resolves `apache-airflow==<version>` before that version exists on PyPI, so those have to come from `--find-links`. ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Opus 5 (1M context) Generated-by: Claude Opus 5 (1M context) 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]
