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