Skip to main content
Version: Early Access

Digital.ai Release 25.1.x Release Notes

Early Access (EA) Releases​

Release Operator 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​

Here's a list of breaking changes in Release 25.1.

End-of-life Notifications​

Here's what is being deprecated or going out of support.

Support for AWS SDK v1 Deprecated​

Support for AWS SDK v1 (awsCredentials, awsRegions) in XL CLI Blueprints was deprecated in Release 25.1 and removed in Release 25.3 and later.

Task Modal Retirement​

As announced in Release 24.3, the Task Modal has been retired in Release 25.1. Users now exclusively use the Task Drawer for creating and managing tasks in the Release user interface. This consolidation enables us to deliver new features faster and provide a more consistent task management experience.

The Task Drawer offers enhanced functionality and a modern interface for managing your tasks. To learn how to use the Task Drawer and explore its features, see:

Contact Digital.ai Customer Success Manager or Digital.ai Support if you need assistance with this transition.

Live Deployments - FluxCD​

Release Plugin for Backstage​

The Release Backstage plugin now includes a Workflow Catalog, allowing you to easily browse, filter, and search workflows across categories such as application lifecycle management, cloud and container, and more—all within the Backstage interface. You can also select a Release instance, view the latest GitHub commit, and run workflows directly from the catalog, streamlining your workflow management experience. For more information, see Workflow catalog.

Enhanced License Counting​

The license counting logic has been improved for more accurate and efficient allocation. Previously, all enabled users (with the "Enabled" toggle set to ON) were counted toward the license limit, even if they had never logged into Release. Now, only enabled users who have logged in at least once or have used Release via the Remote Completion plugin tasks, meaning they have a recorded last active date, will be counted toward the license total. For more details, see License Management.

The Users page now displays License Status for better visibility into license usage. It includes:

  • Active (displayed in green) – The user is counted toward the total license count.

  • Inactive (displayed in gray) – A license is not consumed, meaning the user is not counted toward the license total.

    Permissions

The folder-level template search API now supports title and tag filters, aligning it with the global template search API. This enhancement applies to both the REST API (GET /templates) and the Jython folder API (getTemplates). The update is backward compatible, ensuring that all existing folder API calls continue to function as before.

Create Release Task Enhancements​

Here's what's new and changed with the Create Release task.

Wait for Release to Finish in Create Release Task​

The Create Release task now includes a Wait for Release to Finish option that provides greater control over task completion behavior:

  • When enabled: The parent release pauses until the sub-release completes. The task status reflects the sub-release outcome - succeeding if the sub-release succeeds, or failing if the sub-release fails or is aborted.
  • When disabled: The task completes immediately after starting the sub-release, allowing the parent release to continue independently.

This feature enhances release orchestration by providing better control over parent-child release dependencies and execution flow.

For more information, see Create release task.

Gate Task Enhancements​

Lock Task Permission​

Enhanced controls around task locking and assignment to improve security and task ownership integrity. Only users with the appropriate permissions can lock or unlock tasks.

Key Changes:

  • Users who are not assigned to a task can no longer reassign ownership of locked tasks, even if they have the Perform task transitions or Assign task ownership permissions.
  • Only users with the Lock task permission can lock or unlock tasks. This includes tasks in both templates and releases.
  • Only users assigned to a locked task (either as an owner or a member of the team) can complete, fail, or abort the task. This applies to releases.
  • New permission Assign locked task ownership is introduced - A new permission allows users to reassign the owner or team of locked tasks in a release. This ensures that releases are not blocked if the assigned user is unavailable (e.g., no longer within the organization). This permission is recommended for administrators and applies to releases.

lock tasks

For more information, see Lock Tasks.

Variable Enhancements​

Here are some enhancements around Release variables.

Auto-Fill Variables from Past Releases​

You can now reuse variable values from one of the past 10 completed or aborted releases when you create a new release from a template. Simply select the Pre-fill variables from previous releases check box, select one of the past completed or aborted releases from the drop-down list, and have the values for variables taken from that release. If you want to type new values instead, click Reset to Defaults.

For more information, see Start a Release From a Template.

Multi-region High Availability (HA) Cluster Setup​

We have added support for multi-region HA setup with Pekko-native cluster manager. This setup ensure that if one data center becomes unavailable due to failures or maintenance, the system can switch operations to a standby data center, minimizing downtime and disruption.

Native Pekko Cluster Management​

  • Added native downing provider support
  • Configure with manager = "xlr-pekko-native" in xl-release.conf

Pekko Native Cluster Management​

Pekko's native downing provider for cluster management is now supported, offering improved flexibility and reliability. This implementation includes a downing provider to prevent split-brain scenarios, customizable downing strategies, and the ability to configure cluster formation with specific node requirements. It also offers an HTTP interface for easier remote management and health monitoring, including readiness, liveness, and startup checks.

Cluster Health Check​

Enhanced cluster health monitoring through actuator endpoints, providing more detailed insights into service availability and readiness. These endpoints allow you to check the overall system state and determine whether services are running, ready to accept traffic, or require attention. The newly added actuator endpoints are:

  • Overall health check: http://<node_ip_address>:5516/s/actuator/health
  • Readiness check: http://<node_ip_address>:5516/s/actuator/health/readiness
  • Liveness check: http://<node_ip_address>:5516/s/actuator/health/liveness

Default Trigger Polling Interval Updated to 60 Seconds​

The default trigger polling interval has been updated from 10 to 60 seconds. New polling interval limits have been implemented:

  • Minimum interval: 60 seconds
  • Maximum interval: 86400 seconds (24 hours)
  • Default interval: 60 seconds (when not specified)

You can configure the polling interval in two ways:

  • Interval-based: Specify a number of seconds between executions
  • Cron-based: Use a cron expression for more complex scheduling

When using the YAML configuration or API:

  • You must specify a polling interval within the allowed range
  • If no interval is specified, the system uses the default of 60 seconds
  • Existing triggers will continue to operate with their current configurations, maintaining backward compatibility

For more information, see Configure Trigger Details.

Kubernetes Installation Updates​

  • Simplified truststore setup for Release Runner. For more information, see Set up Truststore for Release
  • Added air-gapped installation support for container plugins.
  • You can now install the Remote Runner (RR) along with the certified OpenShift operator using the xl-cli. This makes the setup process easier and faster by letting you install both components together using a single command. For more information, see Release Installation Options Reference.
  • The Kubernetes blueprints now support separate image version entries for Digital.ai Release and Digital.ai Deploy. This allows you to define different versions for each product in the same blueprint, providing more flexibility for managing upgrades and cross-version compatibility.

UI and Functional Enhancements​

Here are some UI and functional enhancements around Activity Logs, Watchers, and Task Drawer.

Activity Logs (now History) Updates​

Activity logs in Release has been renamed to History. The History page is available contextually with templates, releases, workflow templates and executions, delivery patterns, deliveries, and triggers. For more information, see Release History.

Watcher Changes Tracked​

Changes made to the task Watchers field are now logged in the release History. Adding or removing watchers is recorded in the release history, providing a record of who is following specific tasks. For more information, see Watchers.

watchers history

Copy Task ID​

A new Copy ID option has been added to both the task card and Task Drawer to let you quickly copy the task's ID to the clipboard for later use. For example, copy and use the task ID in API calls.

The copied task ID follows the format: Applications/Folder{identifier}/Release{identifier}/Phase{identifier}/Task{identifier}

threedots

For more information, see Managing Tasks and Components of Task Drawer.

SDK and API Enhancements​

Here are some enhancements around the Release Python SDK and Release REST APIs.

API For a Single Task History​

The API endpoint release activity logs now supports retrieving details for a specific task by including the task ID in the request. For example, GET /api/v1/activities/Applications/Folder{identifier}/Release{identifier}/Phase{identifier}/Task{identifier}.

Plugins and Integrations​

The following plugins and integrations have been updated or added in this release. Plugins are listed alphabetically.

Agility Plugin​

Added Agility query tile to custom dashboards for retrieving and displaying asset information from the Agility server. For more information, see Create an Agility Query Tile.

Airflow Plugin​

New integration enabling Apache Airflow interaction with these tasks:

  • Get DAG Run - Retrieve DAG run information
  • Get Task Instance - Fetch task instance details
  • Trigger DAG Run - Initiate new DAG runs with configuration

AWS Plugin​

Enhanced authentication options:

  • Access Keys
  • None
  • Assume Role ARN

For more information, see Set Up Connection to AWS Server.

Checkmarx Plugin​

Added support for two authentication methods:

  • Basic
  • OAuth2

See Set Up a CheckmarxOne Server.

Confluence Plugin​

New integration for managing Confluence pages:

  • Create and update pages
  • Add comments
  • Delete pages

For more information, see Confluence Plugin.

GitHub Plugin​

Added proxy support using http_proxy or HTTP_PROXY environment variables. See Proxy Support.

Jira Plugin​

Fixed ID/Summary inclusion and sorting in Output Properties.

Slack Plugin​

New integration for Slack workspace automation:

  • Channel creation and archiving
  • Team member management
  • Automated updates

For more information, see Slack Plugin.

SonarQube Plugin​

Added Branch and Pull Request specification support for analysis. For more information, see Create a SonarQube Check Compliance Task.

Octopus Plugin​

Fixed compatibility issue with Create Release task for certain package types.

Bug Fixes and Field Incidents—25.1.0​