Skip to main content
Version: Release 26.1

Digital.ai Release 26.1.x Release Notes

Support Policy​

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​

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

Please review these breaking changes in Release 26.1 before upgrading:

Folder Naming Restrictions with Git Folder Versioning​

Starting with Release 26.1, folders and references to folders cannot be versioned with Git versioning if the folder name contains invalid characters.

The following characters are not allowed in folder names:

<, >, :, ", /, \, |, ?, *

Impact on Upgrades from Release 25.3​

If a version created in Release 25.3 includes:

  • A folder with one or more invalid characters in its name, or
  • A reference to a folder with one or more invalid characters

then applying that version in Release 26.1 may fail to recreate the folder structure correctly.

Folder references with invalid names may exist in Create Release task, Triggers, Dashboards and other configurations.

  1. Identify folder names that contain invalid characters.
  2. Rename the folders by removing or replacing the invalid characters.
  3. Recreate any affected versions to ensure folder structures and references are applied correctly.

For more information, see Saving a New Version.

Experimental External Operator Upgrades​

Upgrading between versions of experimental external operators (Bitnami alternatives) such as PostgreSQL or Ingress-NGINX Controller may not work seamlessly. Review the upgrade documentation for your specific operator before proceeding.

For more information, see Supported External Operators.

Changed Installation Answer Key​

The installation answer key have been renamed:

Old KeyNew Key
PostgresqlInstallPostgresqlType

Update any saved answers files or automation scripts that reference the old key before upgrading. Using the old key will result in an unrecognized-key error during installation.

End-of-life Notifications​

The following features are deprecated or nearing end of support.

Apache Derby Deprecation Notice​

Support for Apache Derby, which could be configured for both Live and Archive databases in demo or test environments (it is not officially supported for production use), is deprecated starting with Release 26.1 and will be removed in Release 26.3.

The Apache Derby project was officially retired in October 2025 and no longer receives bug fixes or security updates. As a result, Apache Derby will not be packaged with or supported by Release 26.3 and later.

If your current Release setup uses Apache Derby, you must replace it with another database before upgrading to Release 26.3.

  • Test and demo environments: You may use H2 database as an alternative.
  • Production environments: Use a supported external database.

For more information, see Configure the SQL repository.

Delivery Insights Integration Plugin​

The xlr-delivery-insights-integration plugin is being deprecated and will no longer be included in the default plugin set starting with Release 26.3.

Git Folder Versioning Improvements​

GitOps-enabled folder versioning now includes improvements that streamline configuration management and version control operations.

Version Comparison​

With the new Compare functionality, Release makes validation, troubleshooting, and collaboration easier by clearly showing changes between versions.

You can now compare two saved versions, or a saved version with the current folder state in Release.

GitOps Comparison Example

During comparison, files are shown by change type:

  • Modified – The file exists in both versions but has changes
  • Added – The file exists in the main version but not in the version being compared
  • Removed – The file does not exist in the main version but exists in the version being compared
  • Unchanged – Files with no changes are not highlighted

GitOps File Dropdown Explorer

File changes are displayed using standard Git notation - additions are highlighted in green, removals in red, unchanged content has no highlighting.

For more information, see Comparing Versions.

Version Actions​

Each version now has the following additional quick actions available in the ellipsis menu (ellipsis menu):

  • Compare with current state – View differences between a saved version and the current configuration in Release
  • Copy commit hash – Copy the full commit hash for reference

These updates make it easier to manage, compare, and track folder versions across your Release environments.

For more information, see Version Actions.

Git Folder Versioning Indicator​

To indicate Git-versioned folders, folders with Git versioning configured now display a Git icon. When a version is applied for a folder, the version number is shown alongside the folder name. The Git icon appears in the top menu folder selector and on the Folders page.

Gitops Versioning indicator

For more information, see Git Folder Versioning Indicator.

Filtering Improvements​

Release 26.1 introduces a more consistent filtering experience across the Tasks, Templates, Workflow Templates, Workflow Executions, and Runners pages. Filters are now easier to review and manage through the Filters drawer and filter panel.

Tasks​

The Tasks page has been reorganized to help you find what you need. Use the free-text search to filter tasks by Title, or open the Filters drawer for additional options such as ownership, status, folder, active range, and tags.

You can sort tasks by multiple fields:

  • Due date – Sort by due date, with the soonest due tasks appearing first.
  • Start date – Sort by when tasks start, with earliest started or upcoming tasks first.
  • Status – Sort by task status, showing Failed/Failing tasks first, followed by In Progress, then Planned.

A new Unassigned option is available in the Task Ownership filter. This option shows tasks that have neither a user nor a team assigned to them.

note

If a task is assigned to a user or team through a variable and is in Planned or Pending status, it will appear when applying the All Tasks option, not under Unassigned. In this case, the assignment is still stored as a variable. The variable is resolved to the actual user or team only when viewed in the Release flow or when the task starts.

For more information, see Filtering Tasks.

Templates and Workflow Templates​

Both pages now support tag-based filtering with two modes:

  • ALL – Shows templates that contain all selected tags.
  • ANY – Shows templates that contain at least one selected tag.

Additionally, Workflow Templates support category filtering to filter templates based on one or more workflow categories.

For more information, see:

Workflow Executions​

Filtering now aligns with the Releases page and includes:

  • Search by owner – Filter by username or email.
  • My workflow executions – Quick access option above the Owner dropdown.
  • Tag filtering – Supports both ALL and ANY modes.

For more information, see Filtering Workflow Executions.

Filtering Runners​

You can now filter runners using the following attributes:

  • Connection status – Running or Disconnected.
  • State – Enabled or Disabled.
  • Type – Digital.ai or Customer.
  • Cluster – Auto-populated from runner properties.
  • Namespace – Auto-populated from runner properties.
  • Environment – Auto-populated from runner properties.

For more information, see Search and Filter Runners.

UI and Functional Enhancements​

Default Landing Pages​

New setting in Personal Settings > Profile allows configuring which pages appear first when logging in to Release or opening a folder. Each user can configure this preference individually.

  • Default global page – Sets the initial page displayed after logging in. Options: Home (default), Folders, Tasks, Releases, or Templates.
  • Default folder page – Sets the initial page displayed when opening a folder. Options: Releases (default) or Templates.

Profile Page UI Settings

For more information, see Profile Settings.

Connection Enhancements​

The Connections page, available at both the Global and Folder levels, displays the total number of available connections and the counts per connection type. A search bar lets you filter by connection type or name, and the counts update dynamically as filters are applied.

A new View only configured setting is introduced, which shows only the connections that are already configured. This helps you quickly review and manage the integrations that are actively in use.

Each connection now also has a direct link, which can be shared by copying the URL from the browser.

Connections Page

For more information, see Connections.

Passwords in Tasks Setting​

A new global setting, Passwords in Tasks, has been added to System Settings. This setting allows administrators to control whether the Allow passwords in all fields option is available in the Releases and Templates properties screens.

By default, this setting is true, which shows the Allow passwords in all fields option in the Releases and Templates properties screens. When the setting is false, the Allow passwords in all fields option is hidden in the Releases and Templates properties screens, and the functionality is disabled for all Releases and Templates.

To configure this setting, navigate to System settings > Releases and Triggers > Passwords in tasks.

For more information, see Passwords in Tasks.

Release Cards Color Update for Finished Releases​

Previously, all finished release cards appeared in gray, making it difficult to distinguish task types. Now, release cards display colors based on task type for both active releases (Planned and In Progress) and finished releases (Completed or Aborted).

Finished releases use lighter, faded versions of their respective task-type colors to clearly indicate that they are complete.

Account Lockout​

The Account Lockout feature improves security by automatically locking internal user accounts after a configurable number of failed login attempts, helping protect against unauthorized access. Changes are made in the xl-release.conf file and require a server restart to take effect. Configurable settings include:

  • Maximum number of failed attempts
  • Lockout duration
  • Whitelisted users

When enabled, a Locked column appears on the Users management page, making it easy to identify and manage locked accounts. Administrators can unlock accounts manually or wait for them to auto‑unlock after the configured duration.

API Updates​

The following API endpoints support the Account Lockout feature:

  • GET /api/v1/users and GET /api/v1/users/{username} - Now include the following fields in the response:

    • failedLoginAttemptCount - The number of failed login attempts for the user.
    • lastFailedLoginAt - Timestamp of the last failed login attempt.
    • accountLocked – Whether the user account is currently locked.

  • POST /api/v1/users/{username}/unlock - New endpoint to programmatically unlock a locked user account. This resets the failed login attempt count and unlocks the account.

For more information, see Configure Account Lockout and the REST API documentation.

Permission Updates​

Release 26.1 introduces the following permission updates:

Release Runner Permissions​

The Runner registration permission has been refined to provide more granular control over runner management. Three global permissions are now available:

  • View runner – Allows users to access the Runners page in Settings > Runners. Without this permission, users will not see the Runners option in the settings menu.
  • Edit runner – Allows users to edit and delete runner configurations. When granted, this permission enables the Edit and Delete options for runners in the runner list.
  • Runner registration – Allows users to register new runners. This permission is a subset of Edit runner and grants access only to register runners.

Admin Permission Restricted to Admin Users​

The Admin global permission is now visible only to users logged in as Admin. Non-admin users cannot see, assign, or modify this permission for themselves or others.

Plugin Manager Access​

Starting with Release 26.1, users with the Edit security permission (without Admin permission) now have view-only access to the Manage plugins page. They can see available and installed plugins but cannot install, remove, upgrade, or upload plugins.

Task Access Control​

Starting with Release 26.1, the Task access page is now restricted to users with the Admin global permission only. Users with the Edit security permission no longer have access to this page, enhancing security by limiting who can define and manage task-level access controls.

For more information, see Configure Global Permissions.

Release Runner Enhancements​

Release 26.1 introduces the following enhancements for Release Runners:

New Configuration Parameters​

  • Skip TLS Verification for Legacy Kubernetes – The RELEASE_RUNNER_SKIP_TLS_LEGACY_K8S configuration parameter lets the runner bypass TLS certificate verification when interacting with legacy Kubernetes clusters. This prevents failures when running Python-based container plugins in environments where certificate validation does not work correctly. Keep this setting disabled by default, and enable it only if you encounter TLS-related errors in older clusters.

  • Executor Labels – The RELEASE_RUNNER_KUBERNETES_EXECUTOR_LABELS configuration parameter adds support for applying custom labels to Release Runner execution pods in Kubernetes environments. Define additional key-value pairs that will be applied to the pods, enabling better organization, resource management, and pod selection in your Kubernetes clusters.

For more information, see Configuration Parameters for Release Runners.

Registry Settings Configuration​

The Digital.ai Release runner registry settings connection is now available only at the global connection level. Registry settings are no longer available in folder connections.

For more information, see Configure Release Runner Registry Settings.

Runner Metadata Configuration​

Release Runners can now be configured with infrastructure metadata including cluster name, environment, data center, and namespace. This metadata enables better organization and filtering of runners.

To view runner metadata,

  1. Navigate to cog icon > Runners.
  2. Click the ellipsis icon (ellipsis menu) for a runner.
  3. Click View metadata.

View Runner Metadata

For more information, see Configure Release Runner Metadata.

Kubernetes Installation Updates​

Release 26.1 introduces Kubernetes version updates, enhancements to the Bitnami alternative external operator installation, XL CLI fixes, and improvements to operator-managed resources.

This release now supports Kubernetes 1.20-1.35 (1.35 is included from Release 25.3.0).

Bitnami Alternative (Experimental) External Operator Enhancements​

The Bitnami alternative (experimental) external operator installation has received several enhancements:

  • Private registry support: Operators can now be pulled from a private container registry.
  • Resource configuration: CPU and memory requests and limits are now configurable for operator-based installations.
  • OpenShift and SCC support: Operator-based installations now support OpenShift, including corrected Security Context Constraints (SCC) handling for all components.
  • Preserve PVC: Persistent Volume Claims can now be preserved for operator-based PostgreSQL.
  • Improved cleanup: Re-ordered cleanup prompts and removal of stale or redundant external operator resources.
  • Fixed resource ordering: Corrected apply order for external Ingress-NGINX resources.

For more information, see Plan Your Kubernetes Installation or Upgrade

Operator-Managed Resources​

  • MAX_RAM_PERCENTAGE configuration is now supported for Release, Central Configuration (CC), and Task Engine containers, enabling better control over JVM heap memory allocation.
  • Custom context root configuration now automatically prepends / if not present.

For more information, see:

Release LLM Integration Container Plugin​

Release 26.1 introduces a new plugin that brings AI-powered automation to Digital.ai Release. The LLM Integration plugin lets you connect to Large Language Model (LLM) providers, call tools on MCP (Model Context Protocol) servers, and build autonomous AI agents that combine reasoning and tool execution - all from within your release workflows.

The following tasks are introduced in this plugin:

  • MCP: List Tools
    Queries an MCP server and returns all available tools with their descriptions and input schemas. Use this to discover what operations a server exposes before calling them.

  • MCP: Call Tool
    Executes a named tool on an MCP server and stores the output. No LLM is involved - it is a direct, deterministic invocation. You can use it wherever you would ordinarily write an integration plugin.

  • AI: Prompt
    Sends a single prompt to an LLM and stores the response. Ideal for processing or transforming text from earlier steps - summarize, classify, extract, translate, or generate content. Supports Release variables using ${variable} syntax.

  • AI: Chat
    Starts a live conversational session with an LLM inside the task's Activity section. The session persists until the user sends Stop chat or the idle timeout expires. Useful for collaborative troubleshooting or human-in-the-loop decisions.

  • AI: Agent
    Gives an LLM access to one or more MCP servers and lets it autonomously plan and execute multi-step workflows to accomplish a goal described in natural language. Each step is recorded in a markdown report in the task's Activity section, so you can trace exactly what the agent did.

For more information, see Release LLM Integration Container Plugin.

Plugins and Integrations​

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

Ansible Automation Controller Plugin​

Added AAP 2.5 or Later checkbox to the server connection configuration. Default is unchecked (uses the older API). When enabled, the plugin switches to the new API for Ansible Automation Platform version 2.5 or later.

For more information, see Ansible Automation Controller Plugin.

Argo CD Plugin​

The following updates are introduced for the ArgoCD plugin:

  • The ArgoCD: Create Application task has been renamed to ArgoCD: Create Or Update Application.
  • Added support to specify Labels for the Argo CD Application when using the ArgoCD: Create Or Update Application task.
    • Labels are defined as key-value pairs and applied to the Application in Argo CD.
    • These labels can be used to organize, search, and filter applications in the Argo CD UI.
  • Added support for multiple sources in the ArgoCD: Create Or Update Application task.
    • Applications can now reference multiple source repositories and configurations.
    • Define sources using the Sources YAML field, which overrides single source configuration when provided.
    • Enables complex deployments where resources come from multiple Git or Helm repositories.
  • Added a new Server-Side Apply option in the ArgoCD: Sync Application task.
    • When enabled, Argo CD performs the sync using Kubernetes Server-Side Apply (SSA).
    • Server-Side Apply allows Kubernetes to merge updates on the server, improving reliability and reducing unintended overwrites.
    • For more information, see Kubernetes Docs: Server-Side Apply.

For more information, see Argo CD Plugin.

Bamboo Plugin​

The following updates are introduced for the Bamboo plugin:

  • You can now use a Personal Access Token (PAT) for Bamboo connections:
    • Authentication Method: Bearer
    • Password: Personal Access Token (PAT)
  • Fixed failTask behavior so the task fails only on build failure when the flag is configured.
  • Enhanced Trigger Deployment task to optionally fetch and print deployment logs, and add Bamboo links to the task description.

For more information, see Bamboo Plugin.

Bitbucket Plugin​

The following updates are introduced for the Bitbucket plugin:

  • Synchronized available tasks between Bitbucket Cloud and Bitbucket Server. Previously, Bitbucket Cloud had fewer tasks.
  • Added a new List Files task to retrieve a complete, structured list of files and folders in a repository for a specified branch or tag.
  • Updated the Approve PR task to replace deprecated API endpoint with the supported version. See Atlassian Deprecation Notice.
  • You can now use a Personal Access Token (PAT) for Bitbucket Server connections:
    • Authentication Method: Bearer
    • Password: Personal Access Token (PAT)
  • Bitbucket Cloud supports username/password authentication only and does not support PAT.

For more information, see Bitbucket Plugin.

Confluence Plugin​

The following updates are introduced for the Confluence plugin:

  • Added a new Is Data Center option in the Confluence: Server connection configuration. This checkbox lets Release determine which type of Confluence instance is being used.
    • When enabled, Release uses Data Center–specific endpoints
    • When disabled, it uses Cloud endpoints.
  • You can now use token-based authentication for Confluence:
    • Username: Enter the email address used to authenticate with Confluence.
    • Token: Enter the Personal Access Token (PAT) used for Confluence requests.
  • Introduced a new Get HTML Page By Title task.
    • Retrieving very large pages may impact release performance. If you expect the page content to be large, increase the Output variable size to avoid truncation.
  • Added credential override fields (Username and Password or token) to all Confluence tasks.
    • These optional fields allow you to override the credentials configured at the connection level for specific task executions.
    • Leave these fields empty to use the connection's default credentials.

For more information, see Confluence Plugin.

Dynatrace Plugin​

The following updates are introduced for the Dynatrace plugin:

  • Added an Allow input autocompletion option to the Dynatrace: Server connection configuration:
    • When enabled, supported fields provide lookup*based suggestions as you type.
    • When disabled, fields behave as plain text inputs without suggestions.
    • Default is True.
  • Updated Get Monitor Executions to fail the task when no availability data is returned.

For more information, see Dynatrace Plugin.

Fortify SSC Plugin​

The following updates are introduced for the Fortify SSC plugin:

  • Fixed an issue where changes in the core product introduced duplicate authentication headers, causing failures in proxy connections.
  • Fixed error when saving tile configuration.

For more information, see Fortify SSC Plugin.

GitLab Plugin​

The following updates are introduced for the GitLab plugin:

  • Added a new Query File Data task to retrieve content from a JSON or YAML file in a GitLab repository. The task accepts Project ID, File path, and Revision, and includes an optional JSON path field to extract a specific value from the file content.

  • Fixed the Query Project task to return the correct Project ID when searching with project name and namespace, avoiding incorrect ID selection from partial matches.

For more information, see GitLab Plugin.

Python SDK Enhancements​

The following updates are introduced for the Python SDK plugin:

  • Lookup Support: The Python SDK now supports lookups, enabling plugins built on it to provide auto-populated values for task input fields.
  • Minimum Python Version: Updated the minimum supported Python version to 3.10.x.
  • Dependency Upgrades: Upgraded bundled dependency versions to improve compatibility and security.
  • Script Location Support: Added scriptLocation hidden property to explicitly define task implementation file paths in type-definitions.yaml.
    • Supports organizing Python task files in subfolders within the src directory.
    • By default, the SDK automatically scans all files in the src directory to find matching task classes.
    • Using explicit scriptLocation reduces scanning overhead and provides better control over project structure.
  • Base Image and SDK Version: All container plugin base images have been upgraded to use python:3.12-alpine with the 26.1.0 version of the Python Integration SDK.
  • Python SDK 26.1.0: Available on PyPI.

For more information, see Digital.ai Release Integration Python SDK Overview.

Remote Completion Plugin​

The Remote Completion plugin now supports Microsoft Graph API as an alternative email source for receiving remote completion responses, in addition to the existing IMAP support. A new Email Source configuration option has been added to support this enhancement.

Email Source – When configuring the Remote Completion: Email Server connection (previously Remote Completion: IMAP Server), you can now select between IMAP or Microsoft Graph API as the email source.

For more information, see Remote Completion Plugin.

ServiceNow Plugin​

The following updates are introduced for the ServiceNow plugin:

  • Enhanced OAuth configuration options in the ServiceNow server connection:
    • Added Grant Type field (External OAuth only) to specify the OAuth grant type (for example, password).
    • Added Scope field (External OAuth only) to define OAuth scope values.
    • These fields apply only when using external OAuth servers. ServiceNow’s native OAuth does not require these configurations.
  • New fields added for the following tasks:
    • Create Change Request: Added Requested Items and Incidents Fixed fields to associate related RITMs and incidents with the change request.
    • Update Change Request: Added Requested Items, Append Requested Items, Incidents Fixed, and Append Incidents Fixed fields. The append options allow you to add new items to existing associations without replacing the existing values.

For more information, see ServiceNow Plugin.

Sonatype Nexus IQ Plugin​

The following updates are introduced for the Sonatype Nexus IQ plugin:

  • Added a new CLI JAR field to the Evaluate Binary task, allowing you to override the global CLI JAR path configured in the server connection.
  • Fixed an issue where changes in the core product introduced duplicate authentication headers, causing failures in proxy connections.

For more information, see Sonatype Nexus IQ Plugin.

Spinnaker Plugin​

The following updates are introduced for the Spinnaker plugin:

  • Get Applications – Retrieves the list of applications available in Spinnaker.
  • Get Pipelines – Retrieves the list of pipelines for a selected application.
  • Get Pipeline Config – Fetches the configuration of a specific pipeline in JSON format.
  • Get Pipeline Execution Status – Retrieves the current status of a pipeline execution by execution ID.
  • Trigger Pipeline – Starts a pipeline execution and returns execution details.

For more information, see Spinnaker Container Plugin.

Tekton Plugin​

The following updates are introduced for the Tekton plugin:

  • Added a Namespace field to the Trigger Pipeline Run task to specify or override the Kubernetes namespace from the provided PipelineRun YAML.
  • Added a Capabilities field to the Tekton: Server (Container) connection for routing tasks to specific Release Runners.
  • Added a new Wait For Pipeline Run (Container) task to wait for a Tekton PipelineRun to complete. This task waits until the specified PipelineRun reaches a terminal state (Succeeded or Failed) and updates the Release task status accordingly.

For more information, see Tekton Container Plugin.

Bug Fixes-26.1.1​

  • D-42408 – Fixed an issue where Jira tasks failed due to use of deprecated API endpoints. The integration now uses supported Jira API versions to ensure compatibility.
  • D-42359 – Fixed an issue where variable mappings for output properties were cleared after a container task failure, causing values to be lost in subsequent runs.
  • D-42583 – Fixed an issue where the Release History page appeared blank even though data was returned, preventing users from viewing history entries.
  • D-42562 – Fixed an issue where updates to task refresh settings were not applied in active release flows, causing task status updates to use incorrect intervals.

Bug Fixes-26.1.0​

  • D-41171 - Fixed incorrect namespace references during SCC installation on OpenShift
    Resolved an issue where the Security Context Constraints (SCC) installation on OpenShift used incorrect resource names and context references when Deploy or Release was installed in a custom namespace. The configuration has been updated to correctly reference the target namespace, ensuring SCC setup completes successfully in non-default environments.
  • D-41496 – Fixed an issue that caused plugin-management operations to fail with external PostgreSQL databases. The temporary pod now bundles the required PostgreSQL libraries.
  • D-41486 – Fixed an issue in XL CLI where running the CLI on RHEL 9 resulted in a Segmentation fault (core dumped) error. The CLI now works correctly on RHEL 9 systems.
  • D-42267 - xl generate now correctly creates the artifacts/ folder, preserving ZIP directory structure during extraction.
  • D-42358 – Fixed an issue where failure handler scripts did not run when a PAT token was provided through a variable instead of directly in the password field, resulting in a missing credentials error.