Skip common.ai provider from Airflow 3.0-3.2 CI compatibility tests - #72550
Skip common.ai provider from Airflow 3.0-3.2 CI compatibility tests#72550rjgoyln wants to merge 2 commits into
Conversation
The provider's dependency floor sits above what those releases' constraint sets allow, so the compatibility jobs installed a mismatched environment and every common.ai test failed at import, turning main's canary red. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
cb60bbc to
29506f5
Compare
The OpenSearch remote logging e2e job failed before any test ran, when docker compose could not bring the environment up. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
| "python-version": "3.10", | ||
| "airflow-version": "3.0.6", | ||
| "remove-providers": "", | ||
| "remove-providers": "common.ai", |
There was a problem hiding this comment.
IIUC, adding common.ai to remove-providers means these three jobs stop running the provider entirely, not just the failing MCP tests. The workflow deletes the wheel before installing and passes the same list as --skip-providers, which breeze turns into --ignore=providers/common/ai/tests.
airflow/.github/workflows/test-providers.yml
Lines 226 to 234 in 2056378
airflow/.github/workflows/test-providers.yml
Line 274 in 2056378
airflow/dev/breeze/src/airflow_breeze/commands/testing_commands.py
Lines 1960 to 1967 in 2056378
#72581 pin devel dependencies to uv.lock, so it doesn't need to skip common.ai provider. WDYT?
There was a problem hiding this comment.
Thanks! I checked #72581, and I agree that approach is better. It addresses the dependency issue without having to skip common.ai, so I’ll close this PR.
Summary
Compat 3.0.6,Compat 3.1.8, andCompat 3.2.2have been failing on main since 2026-09-04, all inproviders/common/ai:cannot import name 'EventSource' from 'httpx2'FastMCP client support is not installedThe issue is caused by the old frozen constraints used by these jobs.
common.airequirespydantic-ai-slim>=2.0.0, but the 3.0-3.2 constraint sets pin incompatible dependency versions. Installing today's provider wheels with--providers-skip-constraintstherefore creates a mixed environment that fails when the provider is imported.Compat 3.3.1passes, and2.11.1already skips this provider.We should not raise the provider's
apache-airflowfloor: Airflow 3.0-3.2 do not impose upper bounds on the relevant dependencies, socommon.aistill supports those releases outside the frozen constraints.The prov:LowestDeps failures in the same canary are an unrelated ibm.mq pre-extras download flake, addressed separately in #71544.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines
🤖 Generated with Claude Code