Skip to main content
Version: Deploy Next

Digital.ai Deploy 26.3.x Release Notes

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 JDK 25
    (JDK 21 is no longer supported)

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

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

  • PostgreSQL: 18.3 / 17.9
    (18.0 and 17.6 are no longer supported)

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

  • Oracle: 26ai LTS / 19c LTS

  • 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:

Java Platform Changes​

note

These changes take effect in Deploy 26.3 and later. No action is required for Deploy 26.1, but advance planning is recommended.

Deploy 26.3 adds JDK 25 support. In JDK 25, the Java Security Manager is permanently disabled, which affects Deploy installations that use the SecurityManager sandbox for Deployfile script execution to isolate host OS and system resources. When enabled on earlier JDKs, the SecurityManager prevents server-side scripts run through the Deployfile functionality from reading host files or accessing system resources. Additionally, free security updates for some JDK 21 distributions end in September 2026.

Action required if:

  • You run Deployfile scripts with the SecurityManager sandbox enabled on JDK 21, and your JDK 21 distribution stops receiving free security updates after September 2026, or
  • You run Deployfile scripts and plan to upgrade to JDK 25.

No action required if:

  • You do not run Deployfile scripts in Deploy,
  • You run Deployfile scripts with the SecurityManager sandbox not enabled, or
  • Your JDK 21 distribution continues to provide free security updates after September 2026 and you are not upgrading to JDK 25.

There is no drop-in replacement for the Java Security Manager. Migrating off the SecurityManager sandbox may require script changes, alternative execution or isolation approaches, and customer-specific governance such as approvals and operational controls. No single security model applies to all installations: the appropriate approach varies by deployment model (VM, Kubernetes, SaaS).

For more information on the SecurityManager sandbox, see SecurityManager configuration.

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.
  • D-43007 - Fixed an issue where file.folder deployments could become unresponsive when deploying applications with identical content to the same installation path. Deploy now handles these deployments correctly without unnecessary delays or timeouts.
  • D-43290 - Fixed an issue where staged deployments of file.Folder artifacts could fail during initial and update deployments. Deploy now correctly handles artifact staging and copy operations throughout the staging lifecycle.