Skip to main content
Version: Early Access

Digital.ai Release 25.3.x Release Notes

Early Access (EA) Releases​

Release Operator Docker Images​

Release Docker Images​

Support Policy​

See Digital.ai Support Policy.

Upgrade Instructions​

The Digital.ai Release upgrade process you use depends on the version from which you are upgrading, and the version to which you want to go.

For upgrade instructions, see:

Breaking Changes​

Breaking changes in Release 25.3 require your attention before upgrading:

Updated System Requirements​

Release 25.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)

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

Webhook Processing: External JMS Dependencies Removed​

In Release 25.3.0, we have simplified webhook event processing by removing the dependency on external JMS message brokers (such as RabbitMQ and ActiveMQ). The system now processes webhook events directly using the database (xlr_ci_event_records) as the event store, which:

  • Simplifies the system architecture by eliminating external message queue dependencies
  • Improves reliability with direct database-backed event processing
  • Reduces operational complexity and maintenance overhead

Important Upgrade Notes:

  • Before upgrading, ensure all webhook events in existing JMS queues are processed as they will not be automatically migrated
  • After the upgrade, all webhook event subscriptions will automatically use the new database-backed processing
  • Any existing JMS-related configurations will be ignored as the system now exclusively uses database-based event handling

Release Tasks Enhancements​

Enhancements in this release make it easier to manage and reuse tasks in Digital.ai Release:

Gate Task Enhancements​

  • A new feature flag called Fail if any dependency fails has been introduced (disabled by default). When this flag is enabled for a gate task, the task will immediately fail (red state) if any one of its dependencies fails—rather than moving to a Failing (yellow) state. This gives teams more control and helps prevent the release from continuing when something goes wrong.
  • With this flag enabled, gate tasks do not recover automatically. Even if the failed dependencies are fixed or retried, the gate task will stay in the Failed state. To continue, you must manually Retry or Skip the task.
  • Gate tasks automatically update their state when dependencies change. If a dependency fails and the Fail if any dependency fails flag is disabled, the gate enters a Failing state (yellow).
  • Nested gate tasks are supported: when a nested gate changes, its parent gate updates accordingly.
  • Adding, removing, or updating dependencies triggers real-time state updates across all related gates, with clear status messages to track changes.

For details, see Gate Tasks Transitions.

Copy and Paste Tasks Across Releases and Templates​

  • You can now copy and paste tasks within the same Release or across different Templates and Releases.
  • Tasks can be pasted into workflows, as long as the task type is supported.
  • This feature streamlines task reuse, making it easier to replicate and modify tasks without starting from scratch.

For details, see: Copy and Paste Task.

Task History in Task Drawer​

We have introduced a new Task History feature within the Task Drawer, providing a comprehensive view of all task-related activities and updates directly in the task interface. This enhancement eliminates the need to navigate away from your current task view while checking activity history.

Key Features:

  • History Tab: A dedicated tab in the Task Drawer that displays a chronological list of all task activities

  • Advanced Filtering:

    • Filter activities by specific users
    • Filter by activity types
    • Quick search functionality for finding specific actions

  • Flexible Sorting Options:

    • Toggle between newest-to-oldest (↓) and oldest-to-newest (↑) using the Sort button
    • Default view shows most recent activities first

  • Detailed Activity Information:

    • User attribution with full name on hover
    • Activity type categorization (e.g., "Task Started", "Task Completed")
    • Precise timestamps for each action
    • Contextual summaries of changes and updates

    Task History View in Task Drawer

For more information, see History Tab.

Deployment Event Triggers​

  • Deployment event triggers now allow Release to listen for deployment status changes from external providers (such as Digital.ai Deploy, ArgoCD, and FluxCD) and automatically start releases based on those events.
  • Users can configure triggers to respond to specific deployment states, filter by application/environment, and dynamically populate release titles and tags using event properties.
  • Improved mapping of JSON event data to template variables, supporting flexible orchestration and live updates.
  • Permissions for managing deployment event triggers are clarified; users need Manage triggers permission and appropriate access to deployment provider resources.

For more information, see Deployment Event Triggers.

Security Improvements​

The following improvements enhance the security of Release:

Personal Access Token Expiration Changes​

  • The Expiration Date and Time is displayed based on the user’s local (browser) timezone.
  • The Expires in value shows the accurate remaining time, regardless of time zone or location.

For more information, see: Set Expiration Period for Personal Access Token

Platform and Integration Enhancements​

These updates expand integration and deployment options:

Provision Release Templates in Backstage Using YAML​

  • You can now provision Digital.ai Release templates in Backstage using inline YAML or YAML files from GitHub.
  • Define Release templates as YAML and apply them directly to Digital.ai Release through Backstage.

For details, see: Provisioning Release Templates in Backstage Using YAML.

Deploy Applications Using Flux CD Container Workflows​

  • Manage Kubernetes application deployments in Digital.ai Release using Flux CD Container Workflows, supporting GitOps deployment patterns.
  • Configure deployment servers, Git repositories, application sources, and manifest generation using the Flux CD Container Plugin.

For details, see: Deploy Applications with the Flux CD Container Workflows.

UI and Functional Enhancements​

Risk Calculation Controls in the UI​

You can now enable or disable risk calculation directly from the Release user interface. This gives administrators greater flexibility in managing how risk scores are calculated and displayed for releases.

  • When enabled, Release calculates risk scores in real time and displays them in the Risk-Aware View and other relevant UI elements.
  • When disabled, risk indicators are hidden from releases, but risk profiles remain configurable.

For more details, see: Risk Calculation

Task Timeout Settings added to UI​

New timeout settings have been added to the Release UI, allowing more control over task timeout durations.

You can now configure timeouts for:

  • Script tasks
  • Custom script tasks
  • Preconditions
  • Failure handlers

For details, see: Task Timeouts

Branch Selection Dropdown in GitOps Version Control​

When configuring GitOps-enabled folder version control, the branch field now provides a dropdown that lists available branches from the connected Git repository.

  • This reduces manual input and prevents typos.
  • You can still enter a branch name manually if needed.

For more details, see: GitOps-enabled Folder Versioning

Plugins and Integrations​

The following plugins and integrations have been updated or added in this release.

Dynatrace Plugin​

New integration enabling Dynatrace interaction with these tasks:

  • Create Synthetic Monitor – Create a new synthetic monitor in Dynatrace directly from a release pipeline.
  • Get Monitor Executions – Retrieve the latest execution results for a specific monitor, with optional filters like location or status.
  • Trigger On-Demand Executions – Run a synthetic monitor (browser or HTTP) on demand, with configurable options like location, execution count, and failure conditions.

For more information, see: Dynatrace Plugin

Tekton Container Plugin​

Introducing a new plugin to integrate Tekton, a Kubernetes-native CI/CD engine, directly into your release pipelines.

This plugin enables interaction with Tekton pipelines using the following tasks:

  • Trigger Pipeline Run (Container) – Start a pipeline run in a specific Kubernetes namespace. Optionally wait for the run to complete and update the task status based on the Tekton result.
  • Get Pipeline Run (Container) – Retrieve the current status of a previously triggered pipeline run. Useful for integrating pipeline results into flow logic.

For more information, see: Tekton Container Plugin