This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 675d3e31675 Cap azure-ai-projects below 2.5 so the CI image passes pip 
check (#73627)
675d3e31675 is described below

commit 675d3e31675ee08e3f67fc99e2f679f7be2b2470
Author: Kaxil Naik <[email protected]>
AuthorDate: Wed Sep 23 17:25:18 2026 +0100

    Cap azure-ai-projects below 2.5 so the CI image passes pip check (#73627)
    
    The openai>=2.47.0,<3 override replaces every package's openai
    requirement, so the resolver no longer rejects azure-ai-projects 2.5+,
    which requires openai>=3.0.0 unconditionally. A lock refresh then moved
    it to 2.7.0 and the CI image build failed in pip check. Cap it at its
    last openai 2.x release, which is what the resolver picks without the
    override.
---
 pyproject.toml | 9 ++++++++-
 uv.lock        | 3 ++-
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/pyproject.toml b/pyproject.toml
index e9e765957b9..1f36fbe38d5 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1451,8 +1451,15 @@ no-build-isolation-package = ["sphinx-redoc"]
 # (pip ignores extra-gated requirements, but not llama-index's unconditional 
cap). pydantic-ai's
 # OpenAI model works against openai 2.x at runtime; the declared floor tracks 
the SDK's httpx2
 # move. Published wheels are unaffected: overrides only shape uv.lock and the 
CI image. Drop this
-# once run-llama/llama_index#22939 and BerriAI/litellm#40317 land and both 
allow openai 3.
+# once run-llama/llama_index#22939 and BerriAI/litellm#40317 land and 
google-cloud-aiplatform
+# lifts its litellm cap (<1.86 below Python 3.14) far enough to reach the 
fixed litellm.
 override-dependencies = ["openai>=2.47.0,<3"]
+# The override replaces every package's openai requirement, not only 
pydantic-ai-slim's, so the
+# resolver no longer rejects a release that needs openai>=3 unconditionally, 
and only `pip check`
+# in the image build catches it. Cap each such package here at its last openai 
2.x release, which
+# is what the resolver would pick without the override. azure-ai-projects 
2.5.0 moved to
+# openai>=3.0.0; the Azure provider needs >=2.2.0.
+constraint-dependencies = ["azure-ai-projects<2.5"]
 # Synchroonize with scripts/ci/prek/upgrade_important_versions.py
 exclude-newer = "4 days"
 
diff --git a/uv.lock b/uv.lock
index ab4c7c10ab1..379468b5ae8 100644
--- a/uv.lock
+++ b/uv.lock
@@ -315,6 +315,7 @@ members = [
     "apache-airflow-task-sdk",
     "apache-airflow-task-sdk-integration-tests",
 ]
+constraints = [{ name = "azure-ai-projects", specifier = "<2.5" }]
 overrides = [{ name = "openai", specifier = ">=2.47.0,<3" }]
 
 [[package]]
@@ -6392,8 +6393,8 @@ requires-dist = [
     { name = "apache-airflow-providers-common-compat", editable = 
"providers/common/compat" },
     { name = "influxdb-client", specifier = ">=1.19.0" },
     { name = "influxdb3-python", specifier = ">=0.12.0" },
-    { name = "pandas", marker = "python_full_version == '3.13.*'", specifier = 
">=2.2.3" },
     { name = "pandas", marker = "python_full_version < '3.13'", specifier = 
">=2.1.2" },
+    { name = "pandas", marker = "python_full_version == '3.13.*'", specifier = 
">=2.2.3" },
     { name = "pandas", marker = "python_full_version >= '3.14'", specifier = 
">=2.3.3" },
     { name = "requests", specifier = ">=2.32.0,<3" },
 ]

Reply via email to