Drop crewai from workspace install path; users install separately

crewai 1.14.x ships tight conservative pins (click~=8.1.7, tomli~=2.0.2,
plus a crewai-cli that pulls textual>=7.5 -> rich>=14.2) that conflict
with Airflow's resolved click 8.3+, tomli 2.4+, and FAB's transitive
rich<14. uv can satisfy the install via override-dependencies, but the
CI image build runs ``pip check`` (see
scripts/docker/install_airflow_when_building_images.sh) which treats
the metadata mismatch as fatal.

The cleanest fix is to keep crewai out of Airflow's resolution entirely:

- Remove the ``[project.optional-dependencies] crewai`` extra from the
  provider pyproject. There's now nothing for uv to resolve against
  crewai's pins -- the root override-dependencies and crewai-* cooldown
  bypass are no longer needed.
- Drop crewai from the provider's dev dependency group.
- Document in docs/hooks/crewai.rst that users ``pip install
  "crewai>=1.14.5"`` themselves after installing common-ai.
- Stub ``crewai`` in ``sys.modules`` for the hook tests (mirrors the
  langchain-stub pattern from #67237 -- justified for crewai because
  the pin conflict makes installation in CI infeasible).

The hook itself is unchanged; users who want it install crewai into
their own venv where they've accepted the pin cascade. The lock no
longer carries crewai / chromadb / onnxruntime entries.

Author: kaxil

providers/common/ai/docs/hooks/crewai.rst

@@ -51,7 +51,7 @@ Supported providers
 
 The hook forwards ``conn.password`` as ``api_key`` and ``conn.host`` as
 ``base_url`` to ``crewai.LLM``. The combinations that work out of the box
-with just the ``crewai`` extra installed:
+with just ``crewai`` installed:
 
 - ``openai/gpt-4o``, ``openai/gpt-4o-mini``
 - ``openai/...`` against an OpenAI-compatible endpoint, with ``host`` pointing
@@ -107,16 +107,26 @@ Parameters
 Dependencies
 ------------
 
-Install the ``crewai`` extra to use this hook::
+Install ``crewai`` separately into your venv after installing the
+``common-ai`` provider::
 
-    pip install apache-airflow-providers-common-ai[crewai]
+    pip install apache-airflow-providers-common-ai
+    pip install "crewai>=1.14.5"
 
-That extra installs ``crewai`` itself (which depends on ``openai`` and
-``anthropic`` at runtime). For other providers, install CrewAI's own
-``litellm`` extra plus the vendor SDK separately, e.g.::
+There is intentionally **no** ``[crewai]`` extra on this provider. crewai
+1.14.x ships tight conservative pins (``click~=8.1.7``, ``tomli~=2.0.2``,
+plus a ``crewai-cli`` co-dependency that pulls ``textual>=7.5`` →
+``rich>=14.2``) that conflict with Airflow's own resolved ``click>=8.3``,
+``tomli>=2.4``, and FAB's transitive ``rich<14``. uv can resolve the
+mismatch via ``override-dependencies``, but the CI image build runs
+``pip check`` afterwards and treats the metadata conflict as fatal. The
+cleanest answer is to keep crewai out of Airflow's lock entirely; users
+who accept the pin cascade install crewai themselves.
 
-    pip install "crewai[litellm]" langchain-mistralai
+For non-OpenAI / non-Anthropic providers, install CrewAI's own
+``litellm`` extra plus the vendor SDK::
 
-The ``crewai`` extra is currently gated on ``python_version < "3.14"`` because
-CrewAI 1.14.x publishes only ``<3.14,>=3.10`` wheels. Newer Python envs will
-silently skip the extra.
+    pip install "crewai[litellm]>=1.14.5" langchain-mistralai
+
+CrewAI 1.14.x publishes wheels for Python 3.10-3.13; 3.14 isn't supported
+upstream yet.

providers/common/ai/pyproject.toml

@@ -103,13 +103,17 @@ dependencies = [
     "llama-index-embeddings-openai>=0.6.0",
     "llama-index-llms-openai>=0.6.0",
 ]
-# crewai pulls chromadb, which transitively requires onnxruntime.
-# onnxruntime >=1.24 dropped cp310 wheels, and crewai itself caps Python
-# to <3.14. Gate the extra to 3.11-3.13 so 3.10 / 3.14 envs don't fail
-# to resolve.
-"crewai" = [
-    'crewai>=1.14.5; python_version >= "3.11" and python_version < "3.14"',
-]
+# crewai is intentionally NOT declared as an optional extra here. crewai
+# 1.14.x ships tight conservative pins (click~=8.1.7, tomli~=2.0.2, and
+# a crewai-cli that pulls textual>=7.5 → rich>=14.2) that conflict with
+# Airflow's own resolved click 8.3+, tomli 2.4+, and FAB's transitive
+# rich<14. uv can satisfy the install via override-dependencies, but
+# Airflow's CI image build runs ``pip check`` afterwards (see
+# scripts/docker/install_airflow_when_building_images.sh) which treats
+# the metadata mismatch as fatal. Users who want the CrewAI hook should
+# ``pip install crewai>=1.14.5`` into their venv after installing
+# common-ai; see docs/hooks/crewai.rst. Hook tests stub ``crewai`` in
+# ``sys.modules``.
 "pdf" = ["pypdf>=4.0.0"]
 "docx" = ["python-docx>=1.0.0"]
 
@@ -129,7 +133,10 @@ dev = [
     "llama-index-core>=0.13.0",
     "llama-index-embeddings-openai>=0.6.0",
     "llama-index-llms-openai>=0.6.0",
-    'crewai>=1.14.5; python_version >= "3.11" and python_version < "3.14"',
+    # crewai deliberately NOT listed here, and also NOT declared as an
+    # optional extra above -- see the comment under
+    # ``[project.optional-dependencies]`` for the pip-check rationale.
+    # Tests stub ``crewai`` in ``sys.modules``.
 ]
 
 # To build docs:

providers/common/ai/tests/unit/common/ai/hooks/test_crewai.py

@@ -16,13 +16,29 @@
 # under the License.
 from __future__ import annotations
 
+import sys
 from unittest.mock import MagicMock, patch
 
 import pytest
 
 from airflow.providers.common.ai.hooks.crewai import CrewAIHook
 
 
+@pytest.fixture(autouse=True)
+def _stub_crewai_module():
+    """Stub ``crewai`` in sys.modules so @patch can resolve targets without
+    the real package installed.
+
+    crewai is intentionally NOT in the provider's dev group (see
+    ``providers/common/ai/pyproject.toml`` for the rationale -- crewai's
+    pins conflict with Airflow's resolved click/tomli/rich and break the
+    CI image build's ``pip check``). Tests have to stub it explicitly.
+    """
+    crewai_mod = MagicMock()
+    with patch.dict(sys.modules, {"crewai": crewai_mod}):
+        yield
+
+
 def _conn(password: str = "", host: str = "", extra: dict | None = None) -> MagicMock:
     mock_conn = MagicMock()
     mock_conn.password = password

pyproject.toml

@@ -1395,6 +1395,23 @@ no-build-isolation-package = ["sphinx-redoc"]
 # Synchroonize with scripts/ci/prek/upgrade_important_versions.py
 exclude-newer = "4 days"
 
+# crewai 1.14.x carries dep pins that conflict with the rest of the Airflow
+# workspace. Override them upstream-style so the resolver picks
+# Airflow-compatible versions and trusts the runtime: click 8.x is
+# API-stable, and rich 14 only added APIs over 13 (no breaking removals
+# crewai-cli/textual hit). Remove these overrides once crewai loosens its
+# pins upstream (https://github.com/crewAIInc/crewAI).
+#   - click: crewai pins ``~=8.1.7`` vs breeze's ``>=8.3.0``.
+#   - rich: crewai-cli's textual>=7.5 pulls ``rich>=14.2`` vs
+#     flask-limiter's ``rich<14`` (FAB transitive).
+#   - tomli: crewai pins ``>=2.0.2,<2.1`` vs airflow-ctl's
+#     datamodel-code-generator==0.33.0 which needs ``tomli>=2.2.1``.
+override-dependencies = [
+    "click>=8.1.7",
+    "rich>=13.6.0",
+    "tomli>=2.0.2",
+]
+
 [tool.uv.exclude-newer-package]
 # Automatically generated exclude-newer-package entries (update_airflow_pyproject_toml.py)
 apache-airflow = false
@@ -1541,6 +1558,17 @@ apache-aurflow-docker-stack = false
 # REMOVE BY 2026-05-01 — once 0.11.8 is older than the global 4-day cooldown
 # this override is redundant and should be deleted along with the line below.
 uv = "12 hours"
+# crewai 1.14.5 and its co-published siblings (crewai-cli, crewai-core,
+# crewai-files, crewai-tools) were released on 2026-05-18. crewai 1.14.0
+# was yanked, so 1.14.5 is the floor we need. Without these overrides the
+# global 4-day cooldown blocks resolution until ~2026-05-22.
+# REMOVE BY 2026-05-23 along with the matching block in
+# [tool.uv.pip.exclude-newer-package] below.
+crewai = "2026-05-19"
+crewai-cli = "2026-05-19"
+crewai-core = "2026-05-19"
+crewai-files = "2026-05-19"
+crewai-tools = "2026-05-19"
 
 [tool.uv.pip]
 # Synchroonize with scripts/ci/prek/upgrade_important_versions.py
@@ -1685,6 +1713,12 @@ apache-aurflow-docker-stack = false
 # `[tool.uv.exclude-newer-package]` above for rationale.
 # REMOVE BY 2026-05-01 along with the matching entry above.
 uv = "12 hours"
+# REMOVE BY 2026-05-23 along with the matching block above.
+crewai = "2026-05-19"
+crewai-cli = "2026-05-19"
+crewai-core = "2026-05-19"
+crewai-files = "2026-05-19"
+crewai-tools = "2026-05-19"
 
 
 [tool.uv.sources]