DAI 26.1 Release Notes

The notes below provide descriptions of the new features and changes introduced in this release of Eggplant DAI.

Any potential compatibility issues are highlighted.

To the extent you are entitled to a copy of the source code for the open source software distributed with this product, a free copy will be provided. Please contact us with your request.

System Requirements

You can find supported operating systems and system recommendations for this release on the Prerequisites page.

Upgrade Notes

Upgrade Notes

• DAI 26.1 is the latest major release of DAI.

• You must upgrade to Eggplant Functional 26.1 before you start your DAI 26.1 upgrade. DAI 26.1 is only compatible with Eggplant Functional (EPF) 26.1.

• The upgrade may take 10-20 minutes to complete.

Take a Backup

Before you upgrade, you need to back up your DAI database folders and configuration file. If there is a problem with your upgrade, you will want to restore your DAI Server to this point. If you have any questions or would like help testing your database before you upgrade, please contact your Technical Success Manager or our Customer Support.

Follow the steps below to back up a DAI Server on Windows:

1. Stop the DAI Server/Windows Service before you take a backup.

2. Back up your database folders (data and minio) and configuration file (config.yml).

3. Restart the DAI Server/Windows Service.

4. Run the installer to for the new version to which you are upgrading.

For information about upgrading container deployments, see Upgrading on the Deploying Eggplant DAI in Containers page.

The online documentation contains the latest information about DAI releases. If you are viewing this documentation online, you are seeing the latest update. If you are using the documentation embedded within DAI, please see the Release Notes on our Documentation website at: https://docs.eggplantsoftware.com/dai/dai-release-notes/ for the latest information.

Release 26.1 (February 2026)

DAI version 26.1 contains the following enhancements and defect fixes:

Important

• DAI 26.2 will be the last release to support HTTP connections to your DAI Server. Starting in DAI version 26.2, TLS (Transport Layer Security) only will be supported. This means you must move your DAI Server to use a secure HTTPS connection rather than HTTP only. This important change enhances application security and results from our Identity Access Management (IAM) solution only supporting HTTPS from the most recent version onwards. To upgrade to DAI 26.2, you will need TLS certificates in place. You should consult your organization’s Cyber/App Security function to arrange these certificates.

• The DAI Public API V3 will be released in a near future, and with it, we will be deprecating and removing Public API v1. Users are advised to make necessary preparations and move to a supported later version.

Features

DAI 26.1 contains the following new feature:

Support for Xray Cloud Test Management Tool Integration

DAI 26.1 adds support for test management tool integrations, starting with Xray Cloud Test Management for Jira. Integrating a third-party test management tool with DAI streamlines test case synchronization and reporting. Once you connect DAI to a test management tool, DAI can automatically synchronize your test cases, requirements, and test results between the two systems. For more information, see Test Management Tool Integrations.

3rd Party Updates

DAI 26.1 includes the following 3rd-party product updates:

Component	Previous Version	Upgraded To
Nginx	1.29.1	1.29.4
RabbitMQ	4.1.4	4.2.2
Postgres	17.7.1	17.7.2
OpenJDK	21.0.8+9	21.0.9+10
Mingit	25.1	25.2

Security Fixes

DAI 26.1 remediates the following security vulnerabilities:

Dependency	Remediated Vulnerabilities
Bug hunting (werkzeug)	CVE-2026-21860 / GHSA-87hc-h4r5-73f7
Marshmallow	GHSA-428g-f7cq-pgp5 / CVE-2025-68480
rllib3	RETEST 26.1.0+2: CVE-2025-50182 / GHSA-48p4-8xcf-vxj5 GHSA-38jv-5279-wg99 / CVE-2026-21441
aiohttp	CVE-2025-69223 / CVE-2025-69224 / CVE-2025-69225 / CVE-2025-69226 / CVE-2025-69227 / CVE-2025-69228 / CVE-2025-69229 / CVE-2025-69230