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.
]]>You can now start Gemini Cloud Assist investigations for failed Airflow tasks.
]]>We strongly recommend to use highly resilient environments for production use cases. Highly resilient environments provide high availability and use built-in redundancy and failover mechanisms to reduce the environment's susceptibility to zonal failures and single point of failure outages.
Resolved an issue in the Kubernetes Pod Operator (KPO) where the Kubernetes client experienced unreliable connections, leading to occasional failures. The fix enhances connection stability through the addition of retry logic for underlying connectivity problems.
New images are available in Cloud Composer 2:
Fixed the CVE-2025-49844 vulnerability. The updated version of the environment component that hosts a Redis-based task queue is available:
New Airflow builds are available in Cloud Composer 3:
]]>Fixed an error where Airflow components failed to start up when multiple
objects with the same name were present in the /dags or /plugins folder in
the environment's bucket.
(Cloud Composer 3) Airflow workers are restarted when they exceed their storage limit.
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.21 and composer-2.9.9-*.
New Airflow builds are available in Cloud Composer 3:
All Cloud Composer environment's GKE clusters will receive maintenance exclusions from November 8, 2025 to December 2, 2025. For more information, see Maintenance exclusions.
]]>(Cloud Composer 2) Configuration of firewall rules for Private IP environments now requires allowing egress traffic on port 19090.
New images are available in Cloud Composer 2:
]]>(Airflow 2.10.5) The apache-airflow-providers-google package was upgraded to version 18.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 17.2.0 to version 18.0.0.
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.20, composer-3-airflow-2.7.3-build.19, composer-2.9.8-*, composer-2.9.7-*.
New Airflow builds are available in Cloud Composer 3:
(Airflow 2.10.5) The apache-airflow-providers-cncf-kubernetes package was
upgraded to version 10.8.2.
For changes in other packages, see the
preinstalled packages changelog.
The default value of the
NO_PROXY
environment variable now includes the IP address of the environment's cluster
Compute Engine metadata server.
(Cloud Composer 2 versions from 2.12.0 to 2.12.3) Fixed a problem where Airflow components in the environment's cluster were running out of ephemeral storage. This change rolls out gradually over several releases to all regions supported by Cloud Composer 2.
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-2.9.6-*, composer-3-airflow-2.7.3-build.17, composer-3-airflow-2.7.3-build.18, composer-3-airflow-2.9.1-build.8, and composer-3-airflow-2.9.1-build.9.
]]>Upgrade checks are now generally available (GA) in Cloud Composer 3 and Cloud Composer 2.
]]>(Airflow 2.10.5) The apache-airflow-providers-google package was upgraded
to version 17.2.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 17.1.0 to version 17.2.0.
(Airflow 2.10.5) The apache-airflow-providers-cncf-kubernetes package was
upgraded to version 10.8.0
from version 10.7.0. For changes in other packages, see the
preinstalled packages changelog.
The GCE_METADATA_TIMEOUT environment variable is changed to reserved. This
change addresses an issue where setting a low timeout value disrupted the
environment's operations that relied on the metadata server.
New Airflow builds are available in Cloud Composer 3:
(Airflow 2.10.5) CloudComposerDAGRunSensor is broken in the
apache-airflow-providers-google package version 17.2.0. This package is used
by Cloud Composer versions and builds with Airflow 2.10.5 available in this
release. If your DAGs use this sensor, we recommend you postpone upgrading
until the issue is resolved.
New images are available in Cloud Composer 2:
The following Cloud Composer versions and builds have reached their end of support period: composer-2.9.4-*, composer-3-airflow-2.9.1 builds from build.0 to build.7, and composer-3-airflow-2.7.3-build.16.
DAG UI now correctly generates error messages about malformed serialized DAG.
]]>Fixed an issue where values of Airflow configuration options were evaluated before being set. As a result, the actual value was set to the evaluated result.
New images are available in Cloud Composer 2:
New Airflow builds are available in Cloud Composer 3:
Fixed Airflow logs not exporting to Cloud Logging because of a GKE version mismatch between Airflow worker and GKE Control plane nodes.
]]>(Cloud Composer 2) Cloud Composer's high availability infrastructure was enhanced to provide greater resilience against zonal outages. This change rolls out gradually over several releases to all regions supported by Cloud Composer 2.
New Airflow builds are available in Cloud Composer 3:
New images are available in Cloud Composer 2:
(Available without upgrading) Cloud Composer 3 now supports DNS resolution for regional service endpoints. You can now reach regional service endpoints from DAGs in your environment. This change is available in Public IP environments without additional configuration. For Private IP environments, an environment must be connected to a VPC network where private endpoints are configured.
The following Cloud Composer versions and builds have reached their end of support period: composer-2.9.2-*, composer-2.9.3-*, and composer-3-airflow-2.7.3-build.15.
You can now check if a Cloud Composer 2 environment's configuration is compatible with Cloud Composer 3. We recommend doing this check before migrating to Cloud Composer 3.
]]>New images are available in Cloud Composer 2:
New Airflow builds are available in Cloud Composer 3:
(Airflow 2.10.5) The apache-airflow-providers-google package was upgraded to version 17.1.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 15.1.0 to version 17.1.0.
Improved the startup times of Airflow workers for environments that have a large number of custom PyPI packages installed.
This feature was announced previously and has finished gradually rolling out to all regions supported by Cloud Composer.
The following Cloud Composer versions and builds have reached their end of support period: composer-2.9.0, composer-2.9.1, and composer-3-airflow-2.7.3 builds from build.5 to build.14.
Airflow UI now shows the correct value of the [core]dags_folder Airflow
configuration option.
(Airflow 2.10.5) The apache-airflow-providers-cncf-kubernetes package was upgraded to version 10.7.0 from version 10.6.1. For changes in other packages, see the preinstalled packages changelog.
(Cloud Composer 2) Moved the update_fab_perms option from [webserver] to
[fab] in the Airflow configuration. The corresponding deprecation warning is
no longer generated in Airflow web server logs.
New images are available in Cloud Composer 2:
(Airflow 2.10.5 only) Added task-level resource consumption Airflow metrics to Cloud Composer.
composer.googleapis.com/workflow/task/cpu_usage: percentage of CPU used by
a task.composer.googleapis.com/workflow/task/mem_usage: percentage of memory used
by a task.Cloud Composer versions 2.8.7 and 2.8.8 have reached their end of support period.
New Airflow builds are available in Cloud Composer 3:
]]>(Cloud Composer 3) The DAGS_FOLDER reserved environment variable now
correctly points to the local directory where DAG files are stored.
New images are available in Cloud Composer 2:
New Airflow builds are available in Cloud Composer 3:
Cloud Composer version 2.8.6 has reached its end of support period.
Fixed an issue that caused unexpected restarts of Airflow component workloads in the environment's cluster.
]]>