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.
August 10, 2026
A new Managed Service for Apache Airflow release has started on August 10, 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) 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 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):
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.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.
July 24, 2026
Starting in September, 2026, Airflow 2.10.5 will no longer be included in new Managed Airflow images and builds. This change will not affect existing images and builds.
Starting in September 2026, we are changing the version support policy for Managed Airflow (Gen 2) to align it with the Managed Airflow (Gen 3) policy. The changes will affect Airflow 2 versions that we release:
- In Managed Airflow (Gen 2), we will release only new images with Airflow 2.11. New Airflow 2.10.5 images will no longer be released.
- In Managed Airflow (Gen 3) we will keep releasing new builds of Airflow 3 (no changes) and will release only new Airflow 2.11 builds. New Airflow 2.10.5 builds will no longer be released.
July 16, 2026
Airflow 3.1.8 is available in Managed Airflow (Gen 3).
Airflow 3.1.7 is no longer included in Managed Airflow images and builds.
(Airflow 3.1.8) Backported #64031 to fix an issue in the Airflow UI when viewing tasks in non-terminal states (scheduled, running) with "Show Gantt" enabled.
(Airflow 3.1.8) The apache-airflow-providers-google package was upgraded to version 22.2.0.
For more information about changes, see the
apache-airflow-providers-google changelog.
(Airflow 2.11.1) The apache-airflow-providers-google package was upgraded to version 22.2.1.
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):
The following Managed Airflow versions and builds have reached their end of support period: composer-3-airflow-2.10.5-build.9, composer-3-airflow-2.9.3-build.29, composer-2.13.7-airflow-2.9.3, composer-2.13.7-airflow-2.10.5.
July 13, 2026
In Managed Airflow (Gen 3) builds with Airflow 2.11.1 starting from composer-3-airflow-2.11.1-build.7, the Airflow web server requires at least 3 GB of memory (the default amount of memory for a Small environment preset is 4 GB).
If the Airflow web server has less than 3 GB of memory, it might experience intermittent out-of-memory (OOM) issues. To resolve these issues, increase the web server memory to at least 3 GB.
July 07, 2026
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.28, composer-3-airflow-2.10.5-build.0, composer-3-airflow-2.10.5-build.2, composer-3-airflow-2.10.5-build.3, composer-3-airflow-2.10.5-build.4, composer-3-airflow-2.10.5-build.5, composer-3-airflow-2.10.5-build.6, composer-3-airflow-2.10.5-build.7, composer-3-airflow-2.10.5-build.8, composer-2.13.6-airflow-2.9.3, and composer-2.13.6-airflow-2.10.5.
June 29, 2026
New Airflow builds are available in Managed Airflow (Gen 3):
New images are available in Managed Airflow (Gen 2):
June 26, 2026
The apache-airflow-providers-google package was upgraded to version 22.1.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):
The following Managed Airflow versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.25, composer-3-airflow-2.9.3-build.26, composer-3-airflow-2.9.3-build.27, composer-2.13.3-airflow-2.9.3, composer-2.13.4-airflow-2.9.3, composer-2.13.5-airflow-2.9.3, composer-2.13.3-airflow-2.10.5, composer-2.13.4-airflow-2.10.5, composer-2.13.5-airflow-2.10.5.
June 12, 2026
New Managed Airflow (Gen 2) environments created while the Restrict Endpoint Usage organization policy is active now use regional endpoints for services like Cloud Storage, Cloud Logging, Pub/Sub, and Data Lineage. For more information, see Configure environments with Restrict Endpoint Usage policy.
June 08, 2026
Several API dependencies that aren't required by Managed Airflow (Gen 3) are now phased out and must be enabled separately if you want to create Managed Airflow (Gen 2) environments in a new project. This change was announced previously.
The following API dependencies were phased out:
- artifactregistry.googleapis.com
- cloudbuild.googleapis.com
- container.googleapis.com
- pubsub.googleapis.com
The following API dependencies aren't phased out yet and are scheduled to be detached from the Cloud Composer API in the future:
- sqladmin.googleapis.com
Existing Managed Airflow (Gen 3) and Managed Airflow (Gen 2) environments in projects where the Cloud Composer API is already enabled aren't impacted.
You can do the following:
- If your project has only Managed Airflow (Gen 3) environments, then you can manually disable the listed APIs that were phased out.
- If your project has Managed Airflow (Gen 2) environments, then we recommend to keep these APIs enabled because disabling them might lead to environment's malfunction.
- If you want to create Managed Airflow (Gen 2) environments in a new project, you can enable the listed APIs manually or using a Google Cloud CLI command. For more information, see Enable Managed Airflow (Gen 2) dependencies.
- If you use automation scripts to provision Managed Airflow (Gen 2) environments, then make sure that the listed APIs are enabled in addition to the Cloud Composer API.
June 02, 2026
(Managed Airflow Gen 3) You can now access Cloud Run endpoints restricted to internal ingress traffic through your environment's network attachment. This feature is available through gcloud CLI beta commands and beta Cloud Composer API in all Managed Airflow (Gen 3) versions.
May 27, 2026
Managed Service for Apache Airflow now supports Google Cloud tags for environments.
Tags provide a way to create annotations for resources, and conditionally allow or deny policies based on whether a resource has a specific tag.
In Managed Airflow (Gen 3), it is now possible to
create Kubernetes Secrets with the kubernetes.io/dockerconfigjson
secret type
through the beta Cloud Composer API, in addition to the default
Opaque secret type. For more information, see Manage Kubernetes Secrets.
(Airflow 3) The INFO log level filter in Airflow UI now correctly displays log messages with this logging level.
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.24, composer-2.13.2-airflow-2.9.3, composer-2.13.2-airflow-2.10.5.
May 14, 2026
The [scheduler]print_stats_interval Airflow configuration option can now be
overridden in environments with Airflow 2.10.5 and later. This option
previously was blocked.
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.23, composer-3-airflow-2.10.5-build.3, and composer-2.13.1-airflow-*.
The google-api-core preinstalled package versions from 2.28.0 to 2.30.2 might
cause degraded environment performance, which can result in longer times to
execute a task and longer times to move a task from the queued to the executing
state.
Affected Managed Airflow (Gen 3) builds:
- composer-3-airflow-3.1.7-build.0 to composer-3-airflow-3.1.7-build.5
- composer-3-airflow-3.1.0-build.5 to composer-3-airflow-3.1.0-build.10
- composer-3-airflow-2.11.1-build.0
- composer-3-airflow-2.10.5-build.22 to composer-3-airflow-2.10.5-build.33
- composer-3-airflow-2.9.3-build.42 to composer-3-airflow-2.9.3-build.53
Affected Managed Airflow (Gen 2) builds:
- composer-2.16.10-airflow-2.11.1
- composer-2.16.0-airflow-2.10.5 to composer-2.16.10-airflow-2.10.5
- composer-2.16.0-airflow-2.9.3 to composer-2.16.10-airflow-2.9.3
We recommend to upgrade your environment to the following versions, which contain a version of the package where the problem is fixed or isn't present:
- composer-3-airflow-3.1.7-build.7 and later
- composer-3-airflow-2.11.1-build.3 and later
- composer-3-airflow-2.10.5-build.36 and later
- composer-3-airflow-2.9.3-build.54 (contains 2.27.0)
- composer-2.17.0-airflow-2.11.1 and later
- composer-2.17.0-airflow-2.10.5 and later
- composer-2.16.11-airflow-2.11.1 (contains 2.27.0)
- composer-2.16.11-airflow-2.10.5 (contains 2.27.0)
- composer-2.16.11-airflow-2.9.3 (contains 2.27.0)
As a workaround, you can manually install a later version of the
google-api-core package to an affected environment by specifying >=2.30.3
as the required version.
May 11, 2026
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.22 and composer-2.13.0-airflow-*.
May 06, 2026
Managed Airflow (Gen 2) environments can no longer be created in Johannesburg (africa-south1). We're switching this region to supporting only Managed Airflow (Gen 3) environments. Existing Managed Airflow (Gen 2) environments in this region aren't affected by this change.
April 28, 2026
Managed Airflow (Gen 3) environments with Airflow 3 support access with external identities through workforce identity federation starting from version composer-3-airflow-3.1.7-build.7.
The default version of Airflow is changed to 2.11.1.
Fixed an issue where DAGs were imported from snapshots even when the "Skip copying Cloud Storage data" option was selected.
The GOOGLE_CLOUD_PROJECT environment variable is now set on schedulers and
triggerers. It's no longer required to set the project ID explicitly when
configuring the Secret Manager backend.
New Airflow builds are available in Managed Airflow (Gen 3):
New images are available in Managed Airflow (Gen 2):
Airflow 2.9.3 is no longer included in Managed Airflow images and builds.
The following Managed Airflow versions and builds have reached their end of support period:
- composer-3-airflow-2.9.3-build.20
- composer-3-airflow-2.10.2 builds from build.0 to build.13
- composer-2.12.1-airflow-*
April 22, 2026
Managed Service for Apache Airflow supports Gemini Cloud Assist Investigations capabilities. The new troubleshooting agent can now troubleshoot failed Airflow task instances and DAG runs. The feature is available through Gemini Cloud Assist Investigations, which is currently accessible in Private Preview.
April 15, 2026
To more strongly embrace the success and growing customer preference for OSS solutions, Cloud Composer is evolving to become Managed Service for Apache Airflow. This name change provides improved customer understanding of our portfolio while reinforcing our commitment to being the most open cloud ecosystem.
Airflow 3 is now generally available (GA) in Cloud Composer 3 starting from the composer-3-airflow-3.1.7-build.4 Airflow build.
Cloud Composer remote Model Context Protocol (MCP) server is available in Preview.
You can use Cloud Composer remote Model Context Protocol (MCP) server to connect to Cloud Composer from AI applications such as Gemini CLI, ChatGPT, Claude, or in AI applications that you're developing. The Cloud Composer MCP server lets you manage Cloud Composer environments and get details about executed DAG runs and Airflow tasks.
April 10, 2026
Fixed a problem with missing DAG description and schedule in the DAG UI which occurred in environments with Airflow 3 in some cases.
Fixed an issue where DAG descriptions and schedules occasionally weren't displayed in DAG UI for environments with Airflow 3.
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-3.1.7-build.5
- composer-3-airflow-2.11.1-build.1
- composer-3-airflow-2.10.5-build.34 (default)
- composer-3-airflow-2.9.3-build.54
These builds are versions with an extended upgrade timeline.
New images are available in Cloud Composer 2:
- composer-2.16.11-airflow-2.11.1
- composer-2.16.11-airflow-2.10.5 (default)
- composer-2.16.11-airflow-2.9.3
These images are versions with an extended upgrade timeline.
April 01, 2026
Airflow 2.11.1 is available in Cloud Composer 3 and Cloud Composer 2.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
March 27, 2026
Cloud Composer 2 environments can no longer be created in Melbourne (australia-southeast2). We're switching this region to supporting only Cloud Composer 3 environments. Existing Cloud Composer 2 environments in this region aren't affected by this change.
A new Cloud Composer release has started on March 27, 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.1.7) Starting from version composer-3-airflow-3.1.7-build.1, Airflow workers no longer have direct access to the Airflow database of your environment.
This feature was announced previously and has finished gradually rolling out to all regions supported by Cloud Composer 3.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
The following Cloud Composer versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.19 and composer-2.12.0-*.
March 19, 2026
Cloud Composer 2 environments can no longer be created in Berlin (europe-west10) and Dallas (us-south1). We're switching these regions to supporting only Cloud Composer 3 environments. Existing Cloud Composer 2 environments in these regions aren't affected by this change.
(Airflow 3.1.7 in Cloud Composer 3)
The apache-airflow-providers-cncf-kubernetes package was
upgraded to version 10.14.0.
For changes in other packages, see the
preinstalled packages changelog.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
March 17, 2026
(Airflow 3.1.7) Starting from version composer-3-airflow-3.1.7-build.1, Airflow workers no longer have direct access to the Airflow database of your environment.
This change follows the architectural and security improvements introduced in the community version of Airflow 3.0. For more information about an alternative way to export and access the data stored in the Airflow database, see Access the Airflow database.
This change is gradually rolled out to all regions supported by Cloud Composer 3.
(Airflow 3.1.7 in Cloud Composer 3)
The apache-airflow-providers-google package was upgraded to version 20.0.0.
For more information about changes, see the
apache-airflow-providers-google changelog.
(Airflow 3.1.7 in Cloud Composer 3)
The apache-airflow-providers-cncf-kubernetes package was
upgraded to version 10.13.0.
For changes in other packages, see the
preinstalled packages changelog.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
The following Cloud Composer versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.18, composer-3-airflow-2.9.3-build.17, composer-2.11.5-*, and composer-2.11.4-*.
March 10, 2026
Cloud Composer 2 environments can no longer be created in Turin (europe-west12). We're switching this region to supporting only Cloud Composer 3 environments.
March 03, 2026
Airflow 3.1.7 is available in Cloud Composer 3.
Highly Resilient environments are available in environments with Airflow 3 (Preview) starting from Airflow version 3.1.7.
Per-folder roles registration is available in environments with Airflow 3 (Preview) starting from Airflow version 3.1.7.
Airflow 3.1.0 is no longer included in Cloud Composer images and builds.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
February 20, 2026
Cloud Composer API now accepts the new
https://www.googleapis.com/auth/cloudcomposer OAuth scope. This scope
provides access only to the Cloud Composer API and can't be used to call other
Google Cloud APIs.
The enable_private_environment boolean field in the Cloud Composer API is
going to be deprecated in the future. When making direct calls to Cloud
Composer API, use the new networking_type field instead.
This change affects only direct calls to the Cloud Composer API.
Google Cloud CLI commands and the google_composer_environment resource in
Terraform are not affected.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
The following Cloud Composer versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.16 and composer-2.11.3-*.
February 16, 2026
Environment snapshots are available in environments with Airflow 3 (Preview). This change is now rolled out to all regions supported by Cloud Composer 3.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
The following Cloud Composer versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.15 and composer-2.11.2-*.
February 10, 2026
(Available without upgrading in Cloud Composer 3) Fixed load snapshot operations that were failing with invalid configuration error for the recently created snapshots.
(Available without upgrading) Fixed an issue where Airflow workloads used the
Performance Persistent Disk type (pd-ssd) instead of the Standard Persistent
Disk type (pd-standard).
January 29, 2026
The Composer Local Development CLI tool is now available for Airflow 3 (Preview).
Environment snapshots are available in environments with Airflow 3 (Preview).
This feature is gradually rolled out in several releases and is available in the following regions in this release: africa-south1, asia-east1, asia-east2, asia-northeast2, asia-northeast3, asia-south2, asia-southeast2, australia-southeast2, europe-central2, europe-north1, europe-north2, europe-southwest1, europe-west10, europe-west12, europe-west3, europe-west4, europe-west6, europe-west8, europe-west9, me-central1, me-central2, me-west1, northamerica-northeast1, northamerica-northeast2, northamerica-south1, southamerica-east1, southamerica-west1, us-east1, us-east5, us-south1, us-west2, us-west3 and us-west4.
(Cloud Composer 2) Airflow component metrics are now available on the Monitoring dashboard in the Google Cloud console. This feature was previously available only in Cloud Composer 3.
(Available without upgrading) Cloud Composer 3 environment metadata in Cloud Asset Inventory now matches the environment configuration available through the Cloud Composer API, including the image version format.
(Airflow 2) The Dag Details view in Airflow UI now scrolls correctly when the "Run config" field contains long values.
(Airflow 3.1.0 in Cloud Composer 3)
The apache-airflow-providers-google package was upgraded to version 19.4.0.
For more information about changes, see the
apache-airflow-providers-google changelog.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
The following Cloud Composer versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.14 and composer-2.11.1-*.
January 14, 2026
Database retention policy is now available in environments with Airflow 3, starting with composer-3-airflow-3.1.0-build.5. This change is now rolled out to all regions supported by Cloud Composer 3.
Cloud Composer 3 environments no longer consume the Cloud SQL Admin API quota in the customer project.
Improved error handling when an invalid Airflow version is specified during environment creation.
(Airflow 3.1.0 in Cloud Composer 3)
The apache-airflow-providers-google package was upgraded to version 19.2.0.
For more information about changes, see the apache-airflow-providers-google changelog.
(Airflow 3.1.0 in Cloud Composer 3)
The apache-airflow-providers-cncf-kubernetes
package was
upgraded to version 10.11.1.
For changes in other packages, see the
preinstalled packages changelog.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
The following Cloud Composer versions and builds have reached their end of support period: composer-3-airflow-2.9.3-build.12, composer-2.10.2-airflow-2.9.3, composer-2.10.2-airflow-2.10.2.
December 23, 2025
Environments with Cloud Composer 2 versions 2.16.0 and 2.16.1 might experience a known issue with the reporting of metrics. You can observe a few skipped data points in the reported metrics and see error messages about the airflow-monitoring pod restarts in the environment logs.
This issue doesn't affect the environment's functionality. The environment is still operational and the environment health and monitoring information is reported correctly. You can ignore the error messages.