Composer 3

Google supports anAirflow build for a period of timeafter it was released:

• 0-12 months from the release date: Cloud Composer 3environments running this Airflow build are supported.

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

  After an Airflow build is no longer supported, environmentsrunning this Airflow build are also unsupported and entirely user-managed.

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

• You can still use an environment with an Airflow build that is no longersupported. The environment still works, you can keep using it, and you canupgrade it to asupported Airflow build.

• In some cases, an upgrade to a later Airflow version or build isthe only available solution for a security vulnerability.

Composer 2

Google supportsCloud Composer 2 versions for a period oftime after the version's release:

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

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

  Important: In some cases, an upgrade to a more recentCloud Composer and Airflow version is the only availablesolution for a security vulnerability.

You can use Cloud Composer versions after the date they areno longer supported. For example, if your environment is based on aCloud Composer version that is past the support period, theenvironment still works and you can keep using it. In this case, we recommendyou toupgrade your environment to asupported version.

Composer 1

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

Composer 3

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

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

Composer 2

For a list of Airflow versions supported in each Cloud Composerversion, see thelist of Cloud Composer versions.

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

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

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

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

• When a new patch version of Airflow 2 becomes available inCloud Composer, the corresponding release hastwo patch versions of Airflow 2 available for the same minor versionof Airflow. The previous patch version is then removed in one of the nextreleases.

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

• Cloud Composer canskip some Airflow patch versions betweenreleases of Cloud Composer. In addition, if there arefunctional, quality, or performance issues with a specific patch versionof 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 caninclude 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 releasedversion 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 major 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 ahigher build number. The build number is defined byCloud Composer and not by the Airflow open source project.

Composer 2

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

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

Where:

• composer-2.b.c denotes the minor and patch version ofCloud Composer-managed customizations in Cloud Composer 2.As a general rule, minor versions of Cloud Composer correspondto significant changes in functionality compared to the previous minorversion, such as when the available set of Airflow versions is changed.Patch versions are updated in subsequent releases.

• airflow-x.y.z is the Airflow release, it denotes the major, minor, andpatch version of Airflow that's used in a specificCloud Composer image.

Composer 1

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

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

Where:

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

Composer 3

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

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

  • Thex.y.z format is for the latest build of the specified version ofAirflow. This format is equal to thecomposer-3-airflow-x.y.zversion alias.

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

  • x.y.z-build.t is the specified version and build of Airflow. Thisformat is equal tocomposer-3-airflow-x.y.z-build.t.

Composer 2

• --image-version argument specifies Cloud Composer 2 and Airflowversions:

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

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

  • Thex.y.z format is for the latest version of Cloud Composer 2 andthe specified version of Airflow. This format is equal tothecomposer-2-airflow-x.y.z version alias.

  • Thex.y format is for the latest version of Cloud Composer 2 and thelatest version of Airflow available withinx.y major and minorversions. This format is equal to thecomposer-2-airflow-x.yversion alias.

Composer 1

• --image-version argument specifies Cloud Composer 1 and Airflowversions:

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

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

  • Thex.y.z format is for the latest version of Cloud Composer 1 andthe specified version of Airflow. This format is equal tothecomposer-1-airflow-x.y.z version alias.

  • Thex.y format is for the latest version of Cloud Composer 1 and thelatest version of Airflow available withinx.y major and minor versions. This format is equal to thecomposer-1-airflow-x.y version alias.