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.
December 17, 2025
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.
December 12, 2025
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-*.
December 09, 2025
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-*.
November 24, 2025
We discovered an issue that might impact the reporting of metrics in the following recently released Cloud Composer versions:
- composer-2.15.4-airflow-*
- composer-3-airflow-2.10.5-build.20
- composer-3-airflow-2.9.3-build.40
- composer-3-airflow-3.1.0-build.3
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.
November 17, 2025
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.
November 14, 2025
You can now start Gemini Cloud Assist investigations for failed Airflow tasks.
November 05, 2025
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:
- To apply the fix in Cloud Composer 3, upgrade the Airflow build of your environment to airflow-2.10.5-build.19 or airflow-2.9.3-build.39, or later.
- To apply the fix in Cloud Composer 2, upgrade your environment to Cloud Composer version 2.15.3, or later.
New Airflow builds are available in Cloud Composer 3:
October 30, 2025
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.
October 27, 2025
(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:
October 22, 2025
(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.
October 10, 2025
(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.
October 09, 2025
Upgrade checks are now generally available (GA) in Cloud Composer 3 and Cloud Composer 2.
September 30, 2025
(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.
September 11, 2025
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.
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.
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.
August 21, 2025
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.
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.
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:
July 28, 2025
(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.
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-factoryversion 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-factoryversion 0.23, then check that your DAGs are parsed and are working correctly, and update them if needed. After your DAGs are compatible, installdag-factoryversion 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-factoryto 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.
In Cloud Composer 3, highly resilient environments are available starting from Airflow builds composer-3-airflow-2.10.2-build.13 and composer-3-airflow-2.9.3-build.20.
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
(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.
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.
New Airflow builds are available in Cloud Composer 3:
Cloud Composer versions 2.8.4 and 2.8.5 have reached their end of support period.
New images are available in Cloud Composer 2:
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
(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.
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
(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:
Cloud Composer version 2.8.3 has reached its end of support period.
New images are available in Cloud Composer 2:
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
Fixed an issue that caused Airflow worker and scheduler Pods to be evicted when a large number of tasks was executed.
New images are available in Cloud Composer 2:
New Airflow builds are available in Cloud Composer 3:
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) 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 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 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:
Cloud Composer version 2.8.1 has reached its end of support period.
New images are available in Cloud Composer 2:
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
It is now possible to restart the Airflow web server through Cloud Composer API by using the RestartWebServer method.
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.
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.
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) 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.
(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.
(Airflow 2.9.3) Changes in preinstalled packages:
apache-airflow-providers-standardwas upgraded to 1.0.0 from 0.4.0.aiosqlitewas removed from preinstalled packages.json-merge-patchwas removed from preinstalled packages.time-machinewas removed from preinstalled packages.pyjwtwas downgraded to 2.9.0 from 2.10.1.
(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.
Cloud Composer version 2.8.0 has reached its end of support period.
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
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
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.
(Airflow 2.10.5) Changes in preinstalled packages:
apache-airflow-providers-standardwas upgraded to 1.0.0 from 0.4.0.aiosqlitewas removed from preinstalled packages.json-merge-patchwas removed from preinstalled packages.time-machinewas removed from preinstalled packages.
Improved the environment liveness monitoring. This change addresses some cases of transient failures that caused "Liveness probe failed" warnings in the environment's logs.
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.
(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.2 is no longer included in Cloud Composer images and builds.
The default version of Airflow is changed to 2.10.5.
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
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
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.
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.
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.
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.
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.
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.
(Cloud Composer 3) Key Access Justifications now correctly works for Customer Managed Encryption Keys (CMEK).
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.
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
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
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
(Available without upgrading) Fixed an issue with updating maintenance windows when there is an upcoming Cloud Composer 3 infrastructure operation.
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 Supported classes in the apache-airflow-providers-openlineage documentation for a list of latest supported operators.
For more information about data lineage in Cloud Composer, see Data lineage with Dataplex.
This feature is gradually rolled out. It will be available in us-west1, us-south1, europe-north1, me-west1, asia-northeast2, asia-southeast2, and africa-south1 regions. We plan to provide this feature in other regions in future releases.
(Airflow 2.10.2 and 2.9.3) The apache-airflow-providers-cncf-kubernetes package was upgraded to version 10.3.0 in Cloud Composer 2 images and Cloud Composer 3 builds. For more information about changes, see the apache-airflow-providers-cncf-kubernetes changelog from version 10.1.0 to version 10.3.0.
(Airflow 2.10.2 and 2.9.3) The apache-airflow-providers-google package was upgraded to version 14.0.0 in Cloud Composer 2 images and Cloud Composer 3 builds.
This package is a new major version where many previously deprecated Airflow operators are removed. It is not possible to use these operators in your DAGs.
Make sure that you update your DAGs to use up-to-date alternatives of the removed operators. For more information about removed and deprecated Airflow operators and their up-to-date alternatives, see Deprecated and removed Airflow operators.
For more information about changes, see the apache-airflow-providers-google changelog from version 10.26.0 to version 14.0.0.
(Airflow 2.10.2 and 2.9.3) Changes in preinstalled packages:
apache-airflow-providers-postgreswas upgraded to 6.1.0 from 5.14.0.apache-airflow-providers-smtpwas upgraded to 2.0.0 from 1.9.0.types-requestswas removed from preinstalled packages.
New images are available in Cloud Composer 2:
- composer-2.12.0-airflow-2.10.2 (default)
- composer-2.12.0-airflow-2.9.3
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-2.10.2-build.12 (default)
- composer-3-airflow-2.9.3-build.19
Cloud Composer versions 2.6.4, 2.6.5, and 2.6.6 have reached their end of support period.
March 18, 2025
After April 15, 2025 the database retention policy feature will be enabled by default in newly created Cloud Composer 3 environments.
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 issue with Cloud Composer 2 upgrade operations is now resolved. The upgrade operations are unblocked in all regions.
March 15, 2025
The Custom constraints with Organization Policy feature is now generally available (GA).
This feature provides more granular control over Cloud Composer environment configuration fields. You can use custom organization policies to allow or deny specific configuration values for Cloud Composer environments.
March 14, 2025
March 18, 2025 update: The issue is resolved.
Some upgrade operations for Cloud Composer 2 might lead to unhealthy environments. That is why upgrades for Cloud Composer 2 versions will be blocked until the issue is fully resolved.
March 11, 2025
(Cloud Composer 3) Validation error messages now use the correct format for image versions.
New images are available in Cloud Composer 2:
- composer-2.11.5-airflow-2.10.2 (default)
- composer-2.11.5-airflow-2.9.3
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-2.10.2-build.11 (default)
- composer-3-airflow-2.9.3-build.18
March 05, 2025
You can now specify an order in which Airflow searches for secrets by overriding the
[secrets]backends_order Airflow configuration option.
Fixed an issue in Cloud Composer REST API that allowed some environment.patch operations to succeed when multiple update masks that aren't related to each other were passed in a request. Now operations with such masks fail with an error.
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-2.10.2-build.10 (default)
- composer-3-airflow-2.9.3-build.17
Cloud Composer versions 2.6.2 and 2.6.3 have reached their end of support period.
New images are available in Cloud Composer 2:
- composer-2.11.4-airflow-2.10.2 (default)
- composer-2.11.4-airflow-2.9.3
March 04, 2025
Cloud Composer 3 supports Customer Managed Encryption Keys (CMEK).
February 27, 2025
Database retention policy is available in Cloud Composer 3. You can use this feature to automatically delete older records from the Airflow database, which helps to maintain the Airflow database's size.
February 25, 2025
Cloud Composer 3 is now available in Stockholm (europe-north2). The change is gradually rolling out.
February 21, 2025
Starting April 14, 2025, the Deployment Manager API won't be automatically enabled when you enable Cloud Composer API because this API isn't used by the Cloud Composer service.
February 20, 2025
(Cloud Composer 3) Fixed a problem with configuring access to SMTP servers that don't support user and password authentication. The [smtp]smtp_user and [smtp]smtp_password Airflow configuration options are no longer preconfigured with placeholder values.
Improved the forbidden APIs check. When a new environment is created, Cloud Composer now checks for forbidden APIs that are required by a specific major version of Cloud Composer.
(Airflow 2.10.2 and 2.9.3) Preinstalled packages were changed:
virtualenvwas downgraded from 20.29.1 to 20.28.1
Cloud Composer version 2.6.1 has reached its end of support period.
New images are available in Cloud Composer 2:
- composer-2.11.3-airflow-2.10.2 (default)
- composer-2.11.3-airflow-2.9.3
New Airflow builds are available in Cloud Composer 3:
- composer-3-airflow-2.10.2-build.9 (default)
- composer-3-airflow-2.9.3-build.16
February 13, 2025
(Cloud Composer 3) The GOOGLE_CLOUD_PROJECT environment variable is changed to reserved for Cloud Composer 3. This fixes an issue where creating an environment with this variable failed with a non-specific error.