Release notes

This section provides general information for each DCT version release, including new features, fixed issues, known issues, and deprecated/end-of-life features.

The Supported versions and upgrade matrix shows which versions of Continuous Data and Continuous Compliance are supported with DCT.

Important considerations

Please review these considerations carefully, as they are relevant across DCT in general.

  • Docker-Compose has reached End-of-life (EOL)

    Install or migrate to a Kubernetes, OpenShift, or Appliance deployment for DCT versions 2025.3 and above.

  • DCT Core is now available for all Delphix customers with an active license.
    This edition of DCT grants access to a modern Continuous Data (CD) UI and read-only Continuous Compliance capabilities for up to two CD engines and one CC engine, along with critical platform features like DCT Tags and global access control. More information can be found in the DCT overview page.

  • DCT currently supports Continuous Compliance engines on version 6.0.13.0 and up.

    However, Delphix highly recommends upgrading Compliance engines to version 20.0.0.0 before connecting them to DCT. Please see this technical bulletin for more details.

  • Release cadence change

    Delphix has returned to a bi-monthly release cadence for Continuous Data, Continuous Compliance, and Data Control Tower. This will begin with the January 2025 release, where the next release follows in March.

  • Version naming convention change
    The new version naming convention follows a YYYY.R.M.P format, represented with numerical values.

    • YYYY: Year of distribution

    • R: Release number

    • M: Minor release number

    • P: Patch number

    As an example, the January release is named 2025.1.0.0—distributed in 2025 (YYYY), the first (R) release of the year, a minor release number set to zero (M), and a patch number set to zero (P).

    Following this pattern, the March release will be named 2025.2.0.0—distributed in 2025 (YYYY), the second (R) release of the year, a minor release number set to zero (M), and a patch number set to zero (P).

Related topics