Allow opentelemetry-exporter-prometheus pre-release in candidate constraints resolution - #71110
Merged
Conversation
vatsrahul1001
requested review from
ashb,
gopidesupavan and
potiuk
as code owners
August 4, 2026 16:26
vatsrahul1001
requested review from
amoghrajesh,
bugraoz93,
jason810496 and
jscheffl
as code owners
August 4, 2026 16:26
…traints resolution Follow-up to #71040. airflow-core requires `opentelemetry-exporter-prometheus>=0.47b0`, a package that only ever ships betas (released constraints already pin e.g. `==0.65b0`). The candidate constraints resolution runs `uv pip install ... --prerelease explicit`, which permits a pre-release only for a package some requirement marks as such and drops the if-necessary fallback, so with no explicit mark it fails with 'No solution found'. Add it to `additional_constraints_for_highest_resolution` (the build-side list the failure message points at) rather than the provider-only pre-release list, so it is an always-allowed pre-release across every resolution, matching how it already ships.
vatsrahul1001
force-pushed
the
fix-otel-prerelease-constraints
branch
from
August 5, 2026 02:12
12e6921 to
e8f87d2
Compare
potiuk
approved these changes
Aug 5, 2026
Contributor
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
potiuk
pushed a commit
that referenced
this pull request
Aug 5, 2026
…ndidate constraints resolution (#71110) (#71132) Follow-up to #71040. airflow-core requires `opentelemetry-exporter-prometheus>=0.47b0`, a package that only ever ships betas (released constraints already pin e.g. `==0.65b0`). The candidate constraints resolution runs `uv pip install ... --prerelease explicit`, which permits a pre-release only for a package some requirement marks as such and drops the if-necessary fallback, so with no explicit mark it fails with 'No solution found'. Add it to `additional_constraints_for_highest_resolution` (the build-side list the failure message points at) rather than the provider-only pre-release list, so it is an always-allowed pre-release across every resolution, matching how it already ships. (cherry picked from commit b23fa6b) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
1 task
vatsrahul1001
added a commit
that referenced
this pull request
Aug 5, 2026
…ndidate constraints resolution (#71110) (#71132) Follow-up to #71040. airflow-core requires `opentelemetry-exporter-prometheus>=0.47b0`, a package that only ever ships betas (released constraints already pin e.g. `==0.65b0`). The candidate constraints resolution runs `uv pip install ... --prerelease explicit`, which permits a pre-release only for a package some requirement marks as such and drops the if-necessary fallback, so with no explicit mark it fails with 'No solution found'. Add it to `additional_constraints_for_highest_resolution` (the build-side list the failure message points at) rather than the provider-only pre-release list, so it is an always-allowed pre-release across every resolution, matching how it already ships. (cherry picked from commit b23fa6b) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.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
2 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.
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.0rc0bounds) and drops the if-necessary fallback. airflow-core requiresopentelemetry-exporter-prometheus>=0.47b0— a package that only ever publishes betas (3.3.0's shipped constraints already pinopentelemetry-exporter-prometheus==0.65b0). With no explicit pre-release mark it can no longer resolve, and candidate constraint generation fails:(seen in the
Release constraintsworkflow_dispatch run on v3-3-test).Fix (per @potiuk's feedback): add it to the build-side
additional_constraints_for_highest_resolutionlist inrun_generate_constraints.py— the list the failure message itself points at — rather than the provider-only pre-release list. This marks it as an always-allowed pre-release across every resolution, keeps--prerelease explicitso no unknown third-party beta can sneak in, and only re-allows a beta airflow already requires and ships.Validation: please re-run the
Release constraintsworkflow on the target branch to confirm green (the fullairflow[all]resolution can't be exercised locally). If a second always-beta dep surfaces after this clears, it takes the same one-line list entry.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines — targeted fix to the candidate constraints pre-release allow-list.