Cloud Composer release notes

These release notes apply to the Cloud Composer service. Announcements and information about new or updated features, bug fixes and deprecated functionality is published on this page.

You can also:

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.

October 09, 2025

Upgrade checks are now generally available (GA) in Cloud Composer 3 and Cloud Composer 2.

September 30, 2025

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.

DAG UI now correctly generates error messages about malformed serialized DAG.

(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) 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.

(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.

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.4-*, and composer-3-airflow-2.9.1 builds from build.0 to build.7.

September 11, 2025

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

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.

Fixed Airflow logs not exporting to Cloud Logging because of a GKE version mismatch between Airflow worker and GKE Control plane nodes.

September 03, 2025

(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.

(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.

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 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.2-* and composer-2.9.3-*.

August 21, 2025

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.

Airflow UI now shows the correct value of the [core]dags_folder Airflow configuration option.

(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.

(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.

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.0, composer-2.9.1, and composer-3-airflow-2.7.3 builds from build.5 to build.13.

August 05, 2025

(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.

(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/cpu_usage: percentage of memory used by a task.

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

Cloud Composer versions 2.8.7 and 2.8.8 have reached their end of support period.

July 28, 2025

Fixed an issue that caused unexpected restarts of Airflow component workloads in the environment's cluster.

(Cloud Composer 3) The DAGS_FOLDER reserved environment variable now correctly points to the local directory where DAG files are stored.

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

Cloud Composer version 2.8.6 has reached its end of support period.

July 24, 2025

Web server restarting is is now generally available (GA) in Cloud Composer 2 and Cloud Composer 3.

July 23, 2025

If your environment uses dag-factory package version 0.22, then you might experience DAG failures in Cloud Composer versions that have apache-airflow-providers-cncf-kubernetes package version 10.4.2 or later. At the same time, upgrading the dag-factory package to version 0.23 might require you to update your DAG code to make it compatible.

If your environment uses dag-factory version 0.22, we recommend to do the following:

  • Temporarily postpone upgrading your environment until you're ready to switch to dag-factory version 0.23. Last versions of Cloud Composer that support version 0.22 are composer-3-airflow-2.10.5-build.3, composer-3-airflow-2.9.3-build.23, composer-2.13.1-airflow-2.10.5, and composer-2.13.1-airflow-2.9.3 released on May 14, 2025.
  • When you are ready to upgrade, update your DAGs for compatibility with 0.23. We recommend to do this in a development environment first. Install dag-factory version 0.23, then check that your DAGs are parsed and are working correctly, and update them if needed. After your DAGs are compatible, install dag-factory version 0.23 in your production environment and transfer the updated DAGs. Your environment can now be upgraded to a later version of Cloud Composer or Airflow.
  • If your environment is already upgraded to a later version of Cloud Composer and you experience problems, then update dag-factory to version 0.23 and update your DAGs for compatibility with 0.23.

July 17, 2025

Highly resilient environments are now generally available (GA) in Cloud Composer 3.

July 14, 2025

We're changing the way we provide support dates for Airflow builds in Cloud Composer 3. Before this change, some Airflow builds had their end of support date listed as "To be announced" until a later Airflow version became available. We're deprecating this approach for all builds that are released after July 01, 2025.

We are now providing support dates that depend on a date when a particular Airflow build was released:

  • We are introducing the standard support period of 12 months after the release date.
  • All Airflow builds that didn't have an end of support date when this change was introduced are supported until July 1, 2026. Because of this change, some Airflow builds released before July 1, 2025 are supported for longer than the standard support period.
  • All Airflow builds that had their support date shorter than 12 months are now supported for 12 months since the date of their initial release.
  • All builds released after July 1, 2025 will use the standard support period.

July 09, 2025

We are gradually rolling out a change that switches the default version from Cloud Composer 2 to Cloud Composer 3 in the Cloud Composer API.

In regions where the change is rolled out, a Cloud Composer 3 environment is created by default when a version is not specified in Google Cloud CLI, Cloud Composer API, or Terraform. If you use automation scripts to provision Cloud Composer 2 environments, make sure that you explicitly specify a Cloud Composer 2 version.

In this release, the change is rolling out in the following regions: africa-south1, asia-northeast2, asia-south2, asia-southeast2, europe-southwest1, europe-west10, europe-west12, europe-west8, me-central1, me-central2, me-west1, southamerica-west1, and us-south1.

(Available without upgrading) During Cloud Composer 2 environment operations, a more informative error message is returned when an environment's web server has connectivity issues.

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

Cloud Composer versions 2.8.4 and 2.8.5 have reached their end of support period.

July 02, 2025

Cloud Composer 1 and Cloud Composer 2 environments with version 2.0.x are approaching their end of life. We're planning to deprecate them in the following way:

  • Starting September 15, 2025, you will no longer be able to create new Cloud Composer 1 environments.
  • On September 15, 2026, all Cloud Composer 1 and Cloud Composer 2 version 2.0.x environments will reach their planned end of life, and you won't be able to use them.

Cloud Composer 2 environments with versions later than 2.1.0 and all Cloud Composer 3 environments are not affected by this deprecation.

We recommend planning migration to Cloud Composer 3 or upgrading your Cloud Composer 2 environments to a later version.

July 01, 2025

This release includes internal infrastructure improvements to Cloud Composer. There are no user-visible changes.

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

June 23, 2025

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 is gradually rolling out over several releases. In this release, it's available in asia-east2, asia-northeast3, europe-central2, europe-west9, me-central1, me-west1, northamerica-northeast1, northamerica-northeast2, northamerica-south1, and us-west1 re

(Available without upgrading) Fixed an issue where deleting a Cloud Composer 2 environment could fail when the environment's cluster was in the process of creating a node pool.

(Airflow 2.10.5) The apache-airflow-providers-cncf-kubernetes package was upgraded to version 10.5.0 from version 10.4.2. 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:

Cloud Composer version 2.8.3 has reached its end of support period.

June 16, 2025

We're planning to phase out the APIs that aren't required by Cloud Composer 3.

  • Starting February 27, 2026, the following APIs will become fully detachable. Deactivating these APIs won't cause the deactivation of the Cloud Composer API:

    • artifactregistry.googleapis.com
    • cloudbuild.googleapis.com
    • container.googleapis.com
    • pubsub.googleapis.com
    • sqladmin.googleapis.com

  • Starting May 27, 2026, these APIs will no longer be enabled automatically when you enable the Cloud Composer API. To create Cloud Composer 2 environments in new projects, the group of detached APIs must be enabled manually.

Existing Cloud Composer 3 and Cloud Composer 2 environments in projects where the Cloud Composer API is already enabled will not be impacted. You can do the following:

  • After February 27, 2026, if your project has only Cloud Composer 3 environments, then you can manually disable the detached APIs.
  • After February 27, 2026, if your project has Cloud Composer 2 environments, then we recommend keeping these APIs enabled because disabling them might lead to environment's malfunction.
  • After May 27, 2026, if you use automation scripts to provision Cloud Composer 2 environments, then make sure that the listed APIs are enabled in addition to the Cloud Composer API.

June 13, 2025

Cloud Composer pages in the Cloud Console now support the dark color theme. You can switch to the dark theme on the Appearance page in the Cloud Console.

June 10, 2025

A new Cloud Composer release has started on June 10, 2025. 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.

Fixed an issue that caused Airflow worker and scheduler Pods to be evicted when a large number of tasks was executed.

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

Cloud Composer version 2.8.2 has reached its end of support period.

June 02, 2025

Improved the startup times of Airflow workers for environments that have a large number of custom PyPI packages installed.

This change rolls out gradually. In this release, it's available in asia-east1, asia-northeast2, asia-south1, europe-north1, europe-west3, us-east1, us-south1, and us-west2 regions.

(Cloud Composer 3) If a VPC network is attached to an environment, then all DNS addresses accessed by the Airflow components of the environment are resolved using the Cloud DNS configuration of the VPC network. In particular, Airflow workers that execute DAGs will resolve DNS addresses in this way.

(Cloud Composer 3) All newly created private DNS zones are immediately visible to a Cloud Composer environment. Previously, re-attaching a VPC network was required.

(Cloud Composer 3) It's now possible to use zones with cross-project binding. Before this change, cross-project bound zones weren't supported in Cloud Composer 3.

(Cloud Composer 2) In Cloud Composer versions 2.11.5 and later, log processing is switching to using OpenTelemetry instead of Fluentd.

This change was announced previously and is gradually rolling out over several releases. In this release, it's available in the following regions: asia-east1, asia-east2, asia-northeast2, asia-northeast3, asia-south2, asia-southeast2, australia-southeast1, australia-southeast2, europe-central2, europe-north1, europe-north2, europe-southwest1, europe-west, europe-west10, europe-west12, europe-west6, europe-west8, europe-west9, me-central1, me-central2, me-west1, northamerica-northeast2, northamerica-south1, southamerica-east1, southamerica-west1, us-east5, us-south1, us-west, and us-west3.

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

Cloud Composer version 2.8.1 has reached its end of support period.

May 29, 2025

The Composer Local Development CLI tool is now available in Cloud Composer 3. This tool helps to streamline testing and developing by providing local Airflow environments based on Airflow builds used by Cloud Composer 3.

May 26, 2025

(Cloud Composer 3) New metrics that show the number of active Airflow components are now available for Cloud Composer 3 environments:

  • The number of active schedulers
  • The number of active DAG processors
  • The number of active triggerers
  • The number of active web servers

(Cloud Composer 3) It's now possible to override the default scopes of access tokens in all regions supported by Cloud Composer 3. This fix was announced previously and has finished gradually rolling out.

(Airflow 2.10.5 and 2.9.3) The apache-airflow-providers-cncf-kubernetes package was upgraded to version 10.4.2 from version 10.1.0.

New Airflow builds are available in Cloud Composer 3:

New images are available in Cloud Composer 2:

May 14, 2025

A new Cloud Composer release has started on May 14, 2025. 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.

It is now possible to migrate from Cloud Composer 1 to Cloud Composer 3 using snapshots in all regions supported by Cloud Composer 3. The gradual rollout of this feature is finished.

It is now possible to restart the Airflow web server through Cloud Composer API by using the RestartWebServer method.

The default value of the [scheduler]max_tis_per_query Airflow configuration option is set to 128. This change fixes the issue with DAGs remaining in the scheduled state in some cases.

Cloud Composer 3 and Cloud Composer 2 no longer support files with gzip encoding (content-type=gzip).

Before this change, all files that had gzip encoding, including .py and .zip files, were processed inconsistently by the DAG processor. After this change, the DAG processor skips all files with gzip encoding. This change doesn't apply to regular .zip archives. Airflow still decompresses and processes DAG files contained in archives that have no specified encoding.

This change is gradually rolled out to all regions supported by Cloud Composer, except us-central1, us-east4 and europe-west1. It will be rolled out to the remaining regions in one of the future releases.

(Cloud Composer 3) Fixed an issue where the Airflow scheduler failed to initialize and work properly if a custom email backend was enabled. The Airflow scheduler now supports the following email backends:

  • airflow.providers.sendgrid.utils.emailer.send_email
  • airflow.utils.email.send_email_smtp

This issue affected only the Airflow scheduler. Airflow workers already support these and other backends. If you use an email backend that isn't supported by the scheduler, you can still send email from Airflow workers.

(Cloud Composer 3) Improved the computation of metrics related to snapshots. This change reduces the number of calls made by Cloud Composer to the Cloud Storage API.

(Cloud Composer 2) In Cloud Composer versions 2.11.5 and later, log processing is switching to using OpenTelemetry instead of Fluentd.

This change is gradually rolled out to the asia-south1 and africa-south1 regions. It will be rolled out to more regions in future releases. New and upgraded Cloud Composer 2 environments in the listed regions will get this change.

(Airflow 2.9.3) The apache-airflow-providers-google package was upgraded to version 15.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 14.0.0 to version 15.1.0.

(Airflow 2.9.3) Changes in preinstalled packages:

  • apache-airflow-providers-standard was upgraded to 1.0.0 from 0.4.0.
  • aiosqlite was removed from preinstalled packages.
  • json-merge-patch was removed from preinstalled packages.
  • time-machine was removed from preinstalled packages.
  • pyjwt was downgraded to 2.9.0 from 2.10.1.

New Airflow builds are available in Cloud Composer 3:

  • composer-3-airflow-2.10.5-build.3 (default)
  • composer-3-airflow-2.9.3-build.23

New images are available in Cloud Composer 2:

  • composer-2.13.1-airflow-2.10.5 (default)
  • composer-2.13.1-airflow-2.9.3

Cloud Composer version 2.8.0 has reached its end of support period.

The following Cloud Composer versions have an extended upgrade timeline:

  • composer-3-airflow-2.10.5-build.3
  • composer-3-airflow-2.9.3-build.23
  • composer-2.13.1-airflow-2.10.5
  • composer-2.13.1-airflow-2.9.3

May 07, 2025

Data lineage in Cloud Composer now uses OpenLineage in all regions supported by Cloud Composer. For more information about this feature, see the previous announcement.

For newly created Cloud Composer 3 environments, the minimum amount of memory is changed to 2 GB.

For newly created environments, database retention policy is now enabled by default in Google Cloud CLI, API, and Terraform. Before this change, it was enabled by default only in Google Cloud Console.

Improved the environment liveness monitoring. This change addresses some cases of transient failures that caused "Liveness probe failed" warnings in the environment's logs.

(Airflow 2.10.5) The apache-airflow-providers-google package was upgraded to version 15.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 14.0.0 to version 15.1.0.

(Airflow 2.10.5) Changes in preinstalled packages:

  • apache-airflow-providers-standard was upgraded to 1.0.0 from 0.4.0.
  • aiosqlite was removed from preinstalled packages.
  • json-merge-patch was removed from preinstalled packages.
  • time-machine was removed from preinstalled packages.

The default version of Airflow is changed to 2.10.5.

Airflow 2.10.2 is no longer included in Cloud Composer images and builds.

New Airflow builds are available in Cloud Composer 3:

  • composer-3-airflow-2.10.5-build.2 (default)
  • composer-3-airflow-2.9.3-build.22

New images are available in Cloud Composer 2:

  • composer-2.13.0-airflow-2.10.5 (default)
  • composer-2.13.0-airflow-2.9.3

Cloud Composer versions 2.7.0 and 2.7.1 have reached their end of support period.

May 06, 2025

The Deployment Manager API is no longer automatically enabled when you enable Cloud Composer API because this API isn't used by the Cloud Composer service.

Environments with Cloud Composer versions 2.0.* still rely on the Deployment Manager API for updates, upgrades, and environment deletion. It won't be possible to perform these operations if this API is disabled. We recommend to upgrade your 2.0.* environments to a later version to remove this dependency.

May 05, 2025

It is now possible to migrate from Cloud Composer 1 to Cloud Composer 3 using snapshots. For more information, see the new migration guide.

This feature will gradually roll out to all regions supported by Cloud Composer 3. At the moment it is available in the africa-south1, asia-south1, me-central1, me-central2, me-west1, southamerica-east1, and southamerica-west1 regions.

April 30, 2025

Starting from 5 May, 2025, new Cloud Composer 3 environments will use 1 CPU and 4 GB of memory for the Airflow web server by default. The minimum and maximum values for these parameters will not change.

April 29, 2025

A script for migrating from Cloud Composer 2 to Cloud Composer 3 is now available on GitHub.

For instructions about migrating with the script, see the new migration guide in Cloud Composer documentation.

April 24, 2025

Starting from June 2025, the default version for new Cloud Composer environments changes from Cloud Composer 2 to Cloud Composer 3. New environments will use the latest default Airflow build (composer-3-airflow-2). Currently, the default version is composer-2-airflow-2.

April 17, 2025

Airflow 2.10.5 is available in Cloud Composer.

Database retention policy is now enabled by default in Google Cloud console and remains disabled in Google Cloud CLI, API, and Terraform.

This feature helps to maintain the Airflow database size. You can enable or disable the database retention policy or adjust the retention period for new and existing environments.

The default environment's service account setting is gradually removed in Cloud Composer. After the change, you'll need to explicitly specify a service account when you create a new Cloud Composer environment. For more information about addressing the change, see the eariler announcement of this change.

In this release, the change is rolling out to the following regions: africa-south1, asia-northeast2, asia-south2, australia-southeast2, europe-north2, europe-southwest1, europe-west8, europe-west10, europe-west12, me-central1, me-central2, me-west1, northamerica-northeast2, northamerica-south1, southamerica-west1, us-east7, and us-south1. It will be rolled out to more regions in future releases.

Cloud Composer 2 environments now always use the environment's service account for performing PyPI packages installations:

  • Existing Cloud Composer 2 environments that previously used the default Cloud Build service account now use the environment's service account instead.
  • Cloud Composer 2 environments created in versions 2.10.2 and later already have this change.
  • Cloud Composer 3 environments already use the environment's service account, and are not affected by this change.
  • This change is gradually rolled out to all regions supported by Cloud Composer 2.

Cloud Composer now detects situations when asynchronous tasks are blocked in Airflow triggerers. If a trigger's execution is blocked for more than five minutes, Cloud Composer restarts the triggerer, which solves this transient issue.

(Cloud Composer 3) Key Access Justifications now correctly works for Customer Managed Encryption Keys (CMEK).

The bucket synchronization process doesn't fail if the /plugins folder isn't available in the environment's bucket.

(Cloud Composer 3) It's now possible to override the default scopes of access tokens. Before the fix, the scope always defaulted to https://www.googleapis.com/auth/cloud-platform and https://www.googleapis.com/auth/userinfo.email. This resulted in authentication failures when accessing non-Google Cloud services.

The change is gradually rolled out to the following regions: africa-south1, asia-south2, australia-southeast2, europe-north2, europe-west3, europe-west10, europe-west12, northamerica-south1, southamerica-west1, us-east7, and us-south1. It will be rolled out to more regions in future releases.

New Airflow builds are available in Cloud Composer 3:

  • composer-3-airflow-2.10.5-build.0
  • composer-3-airflow-2.10.2-build.13 (default)
  • composer-3-airflow-2.9.3-build.20

New images are available in Cloud Composer 2:

  • composer-2.12.1-airflow-2.10.5
  • composer-2.12.1-airflow-2.10.2 (default)
  • composer-2.12.1-airflow-2.9.3

Support dates for previous Cloud Composer 3 builds are available. All Cloud Composer 3 builds with Airflow 2.10.2 are supported until April 17, 2026.

April 09, 2025

The Airflow web server in Cloud Composer 3 requires at least 2 GB of memory when an environment is created or updated. This might lead to longer operation times or failures to perform these operations.

As a workaround, when you create a new Cloud Composer 3 environment or upgrade an existing environment, provide at least 2 GB of memory (default value) to the Airflow web server.

April 07, 2025

All Cloud Composer environment's GKE clusters are set up with maintenance exclusions from March 27, 2025 to April 12, 2025. For more information, see Maintenance exclusions.

April 03, 2025

The unification of Cloud Composer 3 billing with BigQuery is paused until further notice. The change was previously scheduled for April 13, 2025.

In recently released Airflow builds of Cloud Composer 3, the Airflow web server requires more CPU to finish its initialization when an environment is created or updated. This might lead to longer operation times or failures to perform these operations.

As a workaround, when you create a new Cloud Composer 3 environment or upgrade an existing environment, provide at least 1 CPU to the Airflow web server.

This issue currently affects composer-3-airflow-2.10.2-build.12 and composer-3-airflow-2.9.3-build.19 Airflow builds.

March 26, 2025

Data lineage in Cloud Composer now uses OpenLineage.

Data lineage support for a specific Airflow operator is now provided by the provider package where the operator is located. See