This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v3-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-3-test by this push:
new 860eac445b4 [v3-3-test] Allow opentelemetry-semantic-conventions
pre-release in constraints resolution (#71177) (#71178)
860eac445b4 is described below
commit 860eac445b48db41cce0f7814628d1eaf94bc822
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Aug 5 20:56:51 2026 +0800
[v3-3-test] Allow opentelemetry-semantic-conventions pre-release in
constraints resolution (#71177) (#71178)
Constraints cut for a release candidate resolve with `--prerelease
explicit`,
which drops the if-necessary fallback and permits a pre-release only where a
requirement marks one. opentelemetry-semantic-conventions has never
published
a final release, so without an explicit mark the resolution has nothing to
satisfy it with and generation fails outright.
Removing the need for this exception is tracked at
https://github.com/apache/airflow/issues/71176
(cherry picked from commit 5af8d6b899e2b365740551fc80fa787d7adfde7b)
Co-authored-by: Jarek Potiuk <[email protected]>
---
scripts/in_container/run_generate_constraints.py | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/scripts/in_container/run_generate_constraints.py
b/scripts/in_container/run_generate_constraints.py
index ba23a0042b0..c1cca95e2c2 100755
--- a/scripts/in_container/run_generate_constraints.py
+++ b/scripts/in_container/run_generate_constraints.py
@@ -537,10 +537,21 @@ def generate_constraints_pypi_providers(config_params:
ConfigParams) -> None:
# if-necessary fallback; without this entry the package cannot resolve
and generation fails
# with "No solution found". Keeping it here (rather than the provider
pre-release list) marks
# it as an always-allowed pre-release across every resolution, matching
how it already ships.
+ # * opentelemetry-semantic-conventions>=0.48b0 — same story: a beta-only
package, pulled in as a
+ # hard dependency of opentelemetry-sdk (via opentelemetry-exporter-otlp
and shared/observability),
+ # so the ``--prerelease explicit`` resolution needs the same explicit
mark. The floor only marks
+ # it as a pre-release and must stay at the version paired with our
``opentelemetry-*>=1.27.0``
+ # floor — opentelemetry-sdk exact-pins the semantic conventions version
it ships with, so a
+ # higher floor here would conflict with any sdk older than that pairing.
+ #
+ # These two are the only pre-releases in the constraints we tag, and
removing the need for the
+ # exception is tracked at https://github.com/apache/airflow/issues/71176
+ #
additional_constraints_for_highest_resolution: list[str] = [
"pyarrow>=22.0.0; python_version >= '3.14'",
"gremlinpython>=3.8.0",
"opentelemetry-exporter-prometheus>=0.47b0",
+ "opentelemetry-semantic-conventions>=0.48b0",
]
# Constraints cut for a release candidate have to pin the candidates
themselves - the providers
