These release notes apply to the Managed Service for Apache Airflow service. Announcements and information about new or updated features, bug fixes and deprecated functionality is published on this page.
You can also:
- Follow Managed Airflow release notes in the Apache Airflow Community workspace on Slack.
- See Cloud Composer version list for more information about Managed Airflow images and support dates.
- Check the Cloud Composer known issues page to learn more about known issues and possible workarounds.
You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
September 02, 2026
A new Managed Service for Apache Airflow release has started on September 02, 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.
Managed Airflow (Gen 3) environments now provide Out-of-Memory (OOM) event logs to help troubleshoot and diagnose memory exhaustion.
Improved Airflow task resilience against transient Kubernetes pod connection issues.
Improved Airflow web server update process during environment upgrade operations.
New Airflow builds are available in Managed Airflow (Gen 3):
New images are available in Managed Airflow (Gen 2):
August 28, 2026
Orchestration Pipelines are now generally available (GA).
August 26, 2026
(Airflow 3.3.1 and 3.2.2) Environments with Airflow 3.3.1 and 3.2.2 now support loading snapshots from environments with Airflow 2.11.1. This feature lets you migrate from Airflow 2.11.1 environments to Airflow 3 using snapshots, provided that your DAGs in Airflow 2.11.1 are compatible with Airflow 3.
This feature is gradually rolling out over several releases. In this release, it's available in the following regions: europe-north1, europe-west3, us-east1, and us-west2.
(Airflow 3.3.1) Backported #71091 to fix a warning about invalid characters for stats reporting generated by the DAG processor for every file.
New Airflow builds are available in Managed Airflow (Gen 3):
New images are available in Managed Airflow (Gen 2):
The following Managed Airflow versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.32, composer-3-airflow-2.10.5-build.12, composer-2.14.0-airflow-2.10.5, composer-2.14.0-airflow-2.9.3.
August 25, 2026
Managed Airflow remote Model Context Protocol (MCP) server is now generally available (GA).
Managed Airflow Agent is now available in Google Cloud Console. The agent can help you understand, diagnose, and resolve issues with failed Airflow tasks and DAG runs, optimize your environment's performance, identify existing or potential issues, bottlenecks, and areas for optimization.
August 20, 2026
A new Managed Service for Apache Airflow release has started on August 20, 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.
Airflow 3.3.1 is available in Managed Airflow (Gen 3).
Airflow 3.1.8 is no longer included in Managed Airflow images and builds.
Composer Local Development CLI tool now supports deployment with Podman in Linux and Windows.
(Airflow 3.2.2, 3.1.8, and 2.11.1)
The apache-airflow-providers-google package was upgraded to version 22.3.0.
For more information about changes, see the
apache-airflow-providers-google changelog.
New Airflow builds are available in Managed Airflow (Gen 3):
New images are available in Managed Airflow (Gen 2):
August 10, 2026
(Managed Airflow Gen 3) Adjusted the formula used to calculate the number of Airflow web server workers based on allocated CPU and memory resources. This update aligns with resource consumption changes in recent Airflow versions, improving web server stability.
(Airflow 3.2.2 and 2.11.1) The [api]rbac_bindings Airflow configuration
option is blocked and it isn't possible to override its value.
New Airflow builds are available in Managed Airflow (Gen 3):
New images are available in Managed Airflow (Gen 2):
August 05, 2026
(Airflow 3.2.2, 3.1.8, and 2.11.1)
The google-cloud-dataproc package was upgraded to version 5.30.0, which
includes support for Managed Service for Apache Spark
flexible instance configurations
(flexible VMs).
This package was upgraded in Airflow 2.10.5 in a previous release.
(Airflow 3.2.2, 3.1.8, and 2.11.1)
The apache-airflow-providers-google package was upgraded to version 22.2.2.
For more information about changes, see the
apache-airflow-providers-google changelog.
New Airflow builds are available in Managed Airflow (Gen 3):
- composer-3-airflow-3.2.2-build.1
- composer-3-airflow-3.1.8-build.3
- composer-3-airflow-2.11.1-build.14 (default)
- composer-3-airflow-2.10.5-build.47
These builds are versions with an extended upgrade timeline.
New images are available in Managed Airflow (Gen 2):
These images are versions with an extended upgrade timeline.
The following Managed Airflow versions and builds have reached their end of support period: composer-3-airflow-2.10.5-build.11, composer-3-airflow-2.9.3-build.31, composer-2.13.9-airflow-2.9.3, and composer-2.13.9-airflow-2.10.5.
July 29, 2026
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.
(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).
(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.
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.
New Airflow builds are available in Managed Airflow (Gen 3):