A new Managed Service for Apache Airflow release has started on June 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.
New Airflow builds are available in Managed Airflow (Gen 3):
New images are available in Managed Airflow (Gen 2):
]]>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.
]]>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.
]]>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:
The following API dependencies aren't phased out yet and are scheduled to be detached from the Cloud Composer API in the future:
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:
(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.
]]>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.
]]>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:
Affected Managed Airflow (Gen 2) builds:
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:
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.
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-*.
]]>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.
]]>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:
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.
]]>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.
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.
]]>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:
These builds are versions with an extended upgrade timeline.
New images are available in Cloud Composer 2:
These images are versions with an extended upgrade timeline.
]]>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:
]]>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-*.
]]>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:
]]>(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-*.
]]>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.
]]>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:
]]>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-*.
]]>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-*.
]]>(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).
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-*.
]]>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.
]]>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.
]]>Extra Large environments are now generally available (GA) in Cloud Composer 3:
You can now use the extra large environment size for new and existing Cloud Composer 3 environments.
The new Extra Large environment preset is available in the Google Cloud console. This preset sets the initial scale and performance configuration for an environment that can support up to several thousand DAGs. For more information about the estimated number of supported DAGs, DAG runs, and tasks, see Environment presets.
Database retention policy is now available in environments with Airflow 3, starting with composer-3-airflow-3.1.0-build.5.
This change is gradually rolled out in several releases and is available in the following regions in this release: africa-south1, asia-east1, asia-northeast2, asia-northeast3, asia-south2, asia-southeast2, asia-southeast3, australia-southeast2, europe-central2, europe-north2, europe-southwest1, europe-west10, europe-west12, 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-east5, us-south1, us-west3, us-west4.
Fixed an issue where the Copy button on the DAG details page in the Airflow UI was copying incorrect content.
(Airflow 3.1.0 in Cloud Composer 3)
The apache-airflow-providers-google package was upgraded to version 19.1.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.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.11, composer-2.10.1-*.
]]>The dates for maintenance exclusions were changed from the dates announced earlier. All Cloud Composer environment's GKE clusters are now set up with maintenance exclusions from December 4, 2025 to January 2, 2026. For more information, see Maintenance exclusions.
Database retention policy is now available in environments with Airflow 3, starting with composer-3-airflow-3.1.0-build.5. This change is gradually rolled out in several releases and is available in the following regions in this release: europe-north1, us-west2, us-east1, europe-west3, asia-east2.
Fixed an issue where composer.googleapis.com/environment/executor/open_slots
and composer.googleapis.com/environment/executor/running_tasks were not
available in environments with Airflow 3.
(Cloud Composer 3) The name format for network attachments created by Cloud Composer was modified to enhance uniqueness. This change applies only to newly created network attachments.
(Cloud Composer 2) Cloud Composer's high availability infrastructure was enhanced to provide greater resilience against zonal outages. This feature was announced previously and has finished gradually rolling out to all regions supported by Cloud Composer.
(Airflow 3.1.0 and 2.10.5) The apache-airflow-providers-google package was
upgraded to version 19.0.0 in Cloud Composer 2 images and Cloud Composer 3
builds.
For more information about changes, see the apache-airflow-providers-google changelog from version 18.0.0 to version 19.0.0.
(Airflow 3.1.0 and 2.10.5) The apache-airflow-providers-cncf-kubernetes
package was
upgraded to version 10.9.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.7.3-build.22, composer-3-airflow-2.7.3-build.23, composer-3-airflow-2.9.3-build.2, composer-3-airflow-2.9.3-build.3, composer-3-airflow-2.9.3-build.4, composer-3-airflow-2.9.3-build.5, composer-3-airflow-2.9.3-build.6, composer-3-airflow-2.9.3-build.7, composer-3-airflow-2.9.3-build.10, composer-2.9.10-*, composer-2.9.11-*, composer-2.10.0-*.
]]>We discovered an issue that might impact the reporting of metrics in the following recently released Cloud Composer versions:
To prevent additional environments from being affected, we have disabled the ability to upgrade existing environments to these versions and to create new environments using these versions. If your environment is already using one of these versions, you can continue to use it as usual. We are working to resolve the issue for all currently affected environments.
]]>New Airflow builds are available in Cloud Composer 3:
All Cloud Composer environment's GKE clusters are set up with maintenance exclusions from December 16, 2025 to January 2, 2026. For more information, see Maintenance exclusions.
]]>