Managed Service for Apache Airflow: New Release and Deprecations

The following Managed Airflow versions and builds have reached their end of support period : composer-3-airflow-2.10.5-build.10, composer-3-airflow-2.9.3-build.30, composer-2.13.8-airflow-2.9.3, and composer-2.13.8-airflow-2.10.5.

Airflow 3.2.2 is available in Managed Airflow (Gen 3).

(Airflow 3.2.2) The Multi-Team Airflow feature isn't available. The [core]multi_team Airflow configuration option is set to False and it isn't possible to override it.

(Managed Airflow Gen 3 with Airflow 2) Default triggerer resources are changing to 1 vCPU and 2 GB memory to match Airflow 3 defaults. This change is available in the Google Cloud CLI, Terraform, and Cloud Composer API and is gradually rolling out in the Google Cloud console.

New Airflow builds are available in Managed Airflow (Gen 3): composer-3-airflow-3.2.2-build.0 composer-3-airflow-3.1.8-build.2 composer-3-airflow-2.11.1-build.13 (default) composer-3-airflow-2.10.5-build.46

New images are available in Managed Airflow (Gen 2): composer-2.17.8-airflow-2.11.1 (default) composer-2.17.8-airflow-2.10.5

(Airflow 3.2.2) Backported #69877 to restore the ability to deliver failure and retry alerts through a pluggable email backend (configured through the [email]email_backend Airflow configuration option).

A correct error message is now generated when an environment creation request fails because of malformed network and subnetwork identifiers.

(Available without upgrading) The correct default task priority weight of 1 is now shown for tasks in the Google Cloud console.

A new Managed Service for Apache Airflow release has started on July 29, 2026 . Get ready for upcoming changes and features as we roll out the new release to all regions. This release is in progress at the moment. Listed changes and features might not be available in some regions yet.