Context
Dependabot has been proposing to bump apache-airflow 2.11.x → 3.x (#60) and apache-airflow-providers-fab → the 3.x line (#61) to resolve advisories that are only patched in Airflow 3.x. These are not safe auto-merges: Airflow 3 has breaking API changes, and #60 silently relaxes the supported-version cap from <3 to <4. Supporting Airflow 3 is a deliberate effort, not a dependency bump.
Current state
After #62 (dev-lock refresh), 65 of the original 86 Dependabot alerts are cleared. The remaining ~21 are all in the dev-only apache-airflow test tree — the published provider only depends on wherobots-python-dbapi + pydantic, so none of these ship to users:
- ~15
apache-airflow CVEs patched only in 3.x
flask, flask-appbuilder, pytest transitives that Airflow 2.x pins below their patched versions
Scope
Supersedes auto-PRs #60 (airflow 3.2.2) and #61 (providers-fab 3.6.4).
Context
Dependabot has been proposing to bump
apache-airflow2.11.x → 3.x (#60) andapache-airflow-providers-fab→ the 3.x line (#61) to resolve advisories that are only patched in Airflow 3.x. These are not safe auto-merges: Airflow 3 has breaking API changes, and #60 silently relaxes the supported-version cap from<3to<4. Supporting Airflow 3 is a deliberate effort, not a dependency bump.Current state
After #62 (dev-lock refresh), 65 of the original 86 Dependabot alerts are cleared. The remaining ~21 are all in the dev-only
apache-airflowtest tree — the published provider only depends onwherobots-python-dbapi+pydantic, so none of these ship to users:apache-airflowCVEs patched only in 3.xflask,flask-appbuilder,pytesttransitives that Airflow 2.x pins below their patched versionsScope
apache-airflowdev constraint accordinglyapache-airflow-providers-fab/ related providers to their 3.x linesuv.lockSupersedes auto-PRs #60 (airflow 3.2.2) and #61 (providers-fab 3.6.4).