Cloud Composer versioning overview

Composer 3

Google supports an Airflow version for a period of time after the initial release:

• If the minor version of Airflow is the latest one available in Cloud Composer 3, all Airflow builds with this minor version are fully supported. The exact end of support date is determined when a new minor version of Airflow becomes available in Cloud Composer 3.

• When a new minor version of Airflow becomes available in Cloud Composer 3, all builds with the previous minor Airflow version are supported for 12 months, starting from that date. If there are several builds that contain the same minor Airflow version, all of them have the same end of full support date.

• After a minor version is no longer fully supported, environments running this version are also unsupported and entirely user-managed. You can still upgrade such an environment to a fully supported Airflow version.

You can create environments with all Airflow builds that are fully supported.

You can still use an environment with an Airflow build that is no longer supported. The environment still works, you can keep using it, and you can still upgrade it to a fully supported version.

Composer 2

Google supports Cloud Composer 2 versions for a period of time after the version release. During this period, Cloud Composer 2 environments that use these versions are fully supported.

Cloud Composer 2 version support is defined as follows:

• 0-12 months from the release date: Cloud Composer 2 environments running these versions are fully supported.

• 12+ months from the release date: Cloud Composer 2 environments running these versions are unsupported.

You can use Cloud Composer versions after the date they are no longer supported. For example, if your environment is based on a Cloud Composer version that is past the support period, the environment still works and you can keep using it. In this case, we recommend you to upgrade your environment to a supported version.

Composer 1

New Cloud Composer 1 versions were released until the end of March 2023. All released Cloud Composer 1 versions follow the same version deprecation policy as Cloud Composer 2 and are supported according to it.

On March 25, 2024, Cloud Composer 1 entered its post-maintenance mode. Google will not release any further updates to Cloud Composer 1, including new versions of Airflow, bugfixes, and security updates. We recommend migration to Cloud Composer 2.

Composer 3

In Cloud Composer 3, new Airflow versions and builds become available as the time goes.

Your environment can function with all previous Airflow versions and builds, and receives updates to its infrastructure components automatically. Each version and build is supported as described in Version deprecation and support, and you can choose to upgrade your Airflow version to a later version or build.

Composer 2

For a list of Airflow versions supported in each Cloud Composer version, see the list of Cloud Composer versions.

• In each release, Cloud Composer 2 supports two minor versions of Airflow 2.

  For example, Cloud Composer 2.4.0 supports Airflow 2.4.* and Airflow 2.5.*.

• For each minor version of Airflow 2, Cloud Composer supports one patch version.

  For example, for Airflow 2.4.*, Cloud Composer supports Airflow 2.4.3.

• When a new patch version of Airflow 2 becomes available in Cloud Composer, the corresponding release has two patch versions of Airflow 2 available for the same minor version of Airflow. The previous patch version is then removed in one of the next releases.

  For example, Cloud Composer 2.3.4 supports both Airflow 2.5.1 and Airflow 2.5.3.

• Cloud Composer can skip some Airflow patch versions between releases of Cloud Composer. In addition, if there are functional, quality, or performance issues with a specific patch version of Airflow, Cloud Composer can also skip this version.

  For example, Airflow 2.1.3 is skipped and Airflow 2.1.4 is available.

• A Cloud Composer release running a stable Airflow version can include Airflow updates that are backported from a later Airflow version.

Composer 1

The latest version of Airflow supported in Cloud Composer 1 is Airflow 2.4.3.

Only Cloud Composer 1 supports Airflow 1.10.15, which is the latest released version of Airflow 1.

Composer 3

Cloud Composer 3 versioning schema captures Airflow versions and builds:

composer-3-airflow-x.y.z-build.t

Where:

• composer-3 is the version of Cloud Composer.
• airflow-x.y.z.build.t is the Airflow version and build. Every next release of the same Airflow version in Cloud Composer 3 has a higher build number. The build number is defined by Cloud Composer and not by the Airflow open source project.

Composer 2

Cloud Composer 2 image versioning schema captures Cloud Composer and Airflow versions:

composer-2.b.c-airflow-x.y.z

Where:

• composer-2.b.c is the version of Cloud Composer-managed customizations
• airflow-x.y.z is the Airflow release

Composer 1

Cloud Composer 1 image versioning schema captures Cloud Composer and Airflow versions:

composer-1.b.c-airflow-x.y.z

Where:

• composer-1.b.c is the version of Cloud Composer-managed customizations
• airflow-x.y.z is the Airflow release

Composer 3

• --image-version argument specifies the Airflow version and build in the composer-3-airflow-x.y.z-build.t format. You can use version aliases, which are resolved by Google Cloud CLI into the full format.

• --airflow-version specifies the Airflow version in the following formats:

  • The x.y.z format is for the latest build of the specified version of Airflow. This format is equal to the composer-3-airflow-x.y.z version alias.

  • The x.y format is for the latest build of Airflow available within x.y major and minor versions. This format is equal to the composer-3-airflow-x.y version alias.

  • x.y.z-build.t is the specified version and build of Airflow. This format is equal to composer-3-airflow-x.y.z-build.t.

Composer 2

• --image-version argument specifies Cloud Composer 2 and Airflow versions:

  • composer-a.b.c-airflow-x.y.z format creates an environment with the specified versions of Cloud Composer and Airflow.
  • Version aliases first resolve to the composer-a.b.c-airflow-x.y.z format and then create an environment with the specified versions of Cloud Composer 2 and Airflow.

• --airflow-version specifies the Airflow version in the following formats:

  • The x.y.z format is for the latest version of Cloud Composer 2 and the specified version of Airflow. This format is equal to the composer-2-airflow-x.y.z version alias.

  • The x.y format is for the latest version of Cloud Composer 2 and the latest version of Airflow available within x.y major and minor versions. This format is equal to the composer-2-airflow-x.y version alias.

Composer 1

• --image-version argument specifies Cloud Composer 1 and Airflow versions:

  • composer-a.b.c-airflow-x.y.z format creates an environment with the specified versions of Cloud Composer and Airflow.
  • Version aliases first resolve to the composer-a.b.c-airflow-x.y.z format and then create an environment with the specified versions of Cloud Composer 1 and Airflow.

• --airflow-version specifies the Airflow version in the following formats:

  • The x.y.z format is for the latest version of Cloud Composer 1 and the specified version of Airflow. This format is equal to the composer-1-airflow-x.y.z version alias.

  • The x.y format is for the latest version of Cloud Composer 1 and the latest version of Airflow available within x.y major and minor versions. This format is equal to the composer-1-airflow-x.y version alias.