vatsrahul1001 opened a new pull request, #71110:
URL: https://github.com/apache/airflow/pull/71110
Follow-up fix to #71040 (candidate constraints resolution).
**Problem:** the RC constraints path runs `uv pip install ... --prerelease
explicit`, which allows a pre-release only for packages an explicit requirement
marks as such (the provider `>=0.0.0rc0` bounds) and **drops the if-necessary
fallback**. But airflow-core requires
`opentelemetry-exporter-prometheus>=0.47b0` — a package that **only ever
publishes betas** (3.3.0's shipped constraints already pin
`opentelemetry-exporter-prometheus==0.65b0`). With no explicit pre-release
mark, it can no longer resolve, and candidate constraint generation fails:
```
× No solution found when resolving dependencies:
apache-airflow-core[all] depends on
opentelemetry-exporter-prometheus>=0.47b0,
but only opentelemetry-exporter-prometheus<0.47b0 is available (as a
non-pre-release)
```
(seen in the `Release constraints` workflow_dispatch run on v3-3-test).
**Fix:** mark `opentelemetry-exporter-prometheus` pre-release-allowed
alongside the providers, keeping `--prerelease explicit` so no *unknown*
third-party beta can sneak into shipped constraints. This only re-allows a beta
that airflow already requires and already ships.
**Validation:** please re-run the `Release constraints` workflow on the
target branch to confirm green (the full `airflow[all]` resolution can't be
exercised locally). If a second always-beta dep surfaces after this clears, it
needs the same one-line allow-list entry.
cc @potiuk (this touches the constraints tooling from #71040 — raising while
you're out to unblock the 3.3.1 RC; happy to adjust the approach on your
return).
##### 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)
— targeted fix to the candidate constraints pre-release allow-list.
--
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]
