Skip to main content
Version: Early Access

Digital.ai Deploy 26.3.x Release Notes

Early Access (EA) Releases​

Deploy Operator​

Support Policy​

For each version of Deploy, we provide maintenance support for 15 months. For more information, see Digital.ai Support Policy.

Upgrade Instructions​

The upgrade process depends on your current and target Digital.ai Release versions.

For upgrade instructions, see:

Updated System Requirements​

Deploy 26.3 supports the following latest versions of Java, operating systems, and databases. Before upgrading, ensure your environment meets the following requirements:

  • JDK: Supports OpenJDK 21
    (Oracle JDK 17 and OpenJDK 17 are no longer supported)

  • Windows Server: 2025, 2022
    (2019 is no longer supported)

  • RHEL: 9.x, 10.x
    (8.x is no longer supported)

  • PostgreSQL: 17.5, 16.9
    (17.2 and 16.6 are no longer supported)

  • PostgreSQL (provided with Bitnami Helm Chart): 17.6

  • MySQL: 8.4 LTS
    (8.0 LTS is no longer supported)

  • SQL Server: 2022 (16.0)
    (2019 (15.0) is no longer supported)

For more information, see Installation Prerequisites.

Breaking Changes​

Breaking changes in Deploy 26.3 require your attention before upgrading:

  • Apache Derby removed: Apache Derby is no longer bundled or supported as an embedded database. Deploy 26.3 uses H2 exclusively as the embedded database for non-production environments. If you are currently using Derby, migrate to a supported production database before upgrading. See Database Setup and Migration Guidance.

End-of-life Notifications​

  • Apache Derby: Apache Derby is no longer supported. Deploy 26.3 uses H2 as the embedded database for non-production environments. Migrate to a supported production database (PostgreSQL, Oracle, MySQL, or SQL Server). For migration steps, see Database Setup and Migration Guidance.

Application-Level Deployment Locking​

Deploying multiple versions of the same application to the same environment at once can now be controlled at the application level. This is useful when your target environment or middleware does not support multiple deployments of the same application running simultaneously.

Set allowConcurrentDeployments to false on udm.Application to queue deployments, only one version proceeds at a time, and waiting deployments start automatically once the lock is released. Defaults to true.

Key behaviors:

  • Lock scope is per application, per environment. The same application deploying to a different environment is never blocked.
  • Different applications are independent. Two applications sharing an environment are never blocked by each other's locking setting.
  • The lock is held for the full deployment lifecycle, including failed deployments awaiting manual intervention. It releases when the deployment finishes, fails, or is aborted.
  • Queue order is not guaranteed. Queued deployments are processed asynchronously.

Allow Concurrent Deployments on new application

For configuration steps and examples, see Native Locking and Concurrency Management for Deployment Tasks.

Kubernetes Installation Updates​

Migration Guides​

Plugins and Integrations​

Bug Fixes-26.3.0​

  • D-43027 - Fixed an issue where static images in the Deploy UI returned 404 errors in the browser. After webpack build changes, image paths resolved to /dist/images where the files were missing. The images are now correctly copied from ciExplorerDist/libs/images to the expected /dist/images location in the deployment package.
  • D-41370 - Fixed a resource leakage issue in parallel deployment operations involving large deployment packages (>1 GB). Under heavy concurrent deployments, leaked resources could exhaust native memory and cause OutOfMemory (OOM) conditions. The fix adds proper resource cleanup to prevent memory exhaustion and improve deployment stability.