github.com/kubeshop/testkube

This release is available in Helm Chart v2.322.3

Improvements ​

• Fixed executions stuck initializing or not finishing due to race conditions caused by MongoDB Replication lag.

This release is available in Helm Chart v2.322.2

Improvements ​

• Fixed workflows filtering by status to correctly display filtered results

• Improved stability and performance of custom views for a smoother, more reliable experience

• Resolved organization/environment settings tabs redirecting to incorrect tabs

• Fixed browser back navigation crashes that occurred on specific application pages

• Improved memory usage of Control Plane when deleting artifacts

This release is available in Helm Chart v2.322.1.

What's new! ​

This release comes with a new way to deploy Runner Agents and several improvements to workflows.

You can now install a Runner Agent using only Helm. Previously a Runner Agent had to be registered using the CLI or UI prior to Helm install. This feature can be used to create Runner Agents for ephemeral environments in a single step. Documentation is available here .

Users can now create custom views to group workflows by any criteria, making it easier to organize workflows that belong together or quickly access frequently used filtered results. These views are shared between all the users of a given environment.

We've added a new Workflow Health indicator that shows a quick visual summary of a workflow's recent stability, helping users understand how reliably it's been running over time, not just surfacing flakiness, but overall consistency. The health score is calculated as PassRate x (1 - FlipRate) and shown as an icon next to each workflow in both list and detail views, using weather-style visuals to represent different health levels.

We've introduced a new Canceled status to distinguish manual cancellations from system-level Aborted executions. Previously, both were marked as Aborted. With updated icons and messaging, users can now clearly see if a test Failed, was Aborted (system error), or Canceled (manual action).

Testkube Copilot has been renamed to Testkube AI Assistant to better reflect its purpose and avoid confusion with similarly named tools. This makes it clearer that the assistant is purpose-built for the Testkube ecosystem.

Improvements and fixes ​

• Workflows search - Revised the way search works. You can now search for workflows using multiple words separated by spaces. The search matches when all the words are contained in the workflow name.

• CLI Artifact Download - Fixed authentication problems with certain cloud providers due to presence of duplicate authentication mechanism.

• Executions Logs - Improved horizontal scrolling for long logs.

• Insights - Fixed an issue where saving changes to an existing report saved a new one instead which led to duplicates.

• Fixed an issue where schedule links would navigate to the wrong workflow.

• Fixed an issue where the correct JUnit test suite icon wasn't displaying properly

• Improved the timestamps displayed within execution details when workflows are still queued.

• Improved handling of JUnit format when working with nested test suites

• Resolved a problem with empty string default values in workflow config settings

• Enhanced the agents dropdown for better usability

• Fixed an issue where your selected agents weren't being preserved when running workflows

• Corrected broken links in the running context that weren't properly directing to workflows

• Fixed a search error that occurred when searching for empty or non-existent values in execution logs

• Resolved a critical security vulnerability (F-2025-4481) related to OAuth account hijacking via redirect URLs

• Strengthened security headers in our nginx configuration for better protection

• Fixed an issue where the Workflow wizard shows an empty preview when combining multiple templates

• Security updates in upstream dependencies.

• Fix API failure when deleting expired API token.

• Artifact cleaning via ENTERPRISE_ARTIFACT_RETENTION_DAYS and ENTERPRISE_ARTIFACT_MAX_STORAGE_SIZE_GB now works as expected.