Versioning in Cloud Data Fusion
Versioning scheme
This page explains versioning in Cloud Data Fusion. You can see thecurrent version support schedule in theVersion support policy.Cloud Data Fusion uses thesemantically versioned industry standard (MAJOR.MINOR.PATCH.REVISION).
- Cloud Data Fusion major version
- If any backwards incompatible changes are introduced, major versions typicallyare incremented. A major version increments the Cloud Data Fusion versionfrom
MAJOR.MINORtoMAJOR+1.MINOR. - Cloud Data Fusion minor version
- Cloud Data Fusion typically releases a new minor version twice a year.The minor version typically includes new features, enhancements, deprecations,bug fixes, and performance improvements. Minor version releases requireupgrading both Cloud Data Fusion instances and pipelines. A minor versionincrements the Cloud Data Fusion version from
MAJOR.MINORtoMAJOR.MINOR+1. - Cloud Data Fusion patch release
- New Cloud Data Fusion patch releases typically include major bug fixes.Patch releases require upgrading both Cloud Data Fusion instances andpipelines.
- Cloud Data Fusion patch revisions
- A patch revision, the fourth suffix, such as 6.9.2.1, includes securityupdates and bug fixes for the Cloud Data Fusion platform. These revisionsonly require upgrading instances. Pipeline upgrades are disassociated andaren't required with patch revisions.
What's next
- Manage patch revisions for Cloud Data Fusion instances.
- Manage version upgrades for pipelines and instances.
- Refer to theavailable version and patch revision upgrades.
- Troubleshoot upgrades.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.