SquashTM Orchestrator 6.1.0 Release Note

Introduction

SquashTM Orchestrator is a set of micro-services to perform automated test execution workflows described in a specific format.

This release note describes the changes of SquashTM Orchestrator version 6.1.0 compared to 6.0.0.

SquashTM Orchestrator 6.1.0 was released on November 10, 2025.

Issue otf-all-in-one-images #79 [Micronaut] Remove java from image
Issue squash-orchestrator #157 🔑 [Micronaut] Remove java from image
Issue squash-orchestrator #412 🔑 [image orchestrator]Revert from OpenSSL to keytool and keep the JVM
Services related to Allure have been removed from the Orchestrator, it is no longer possible to generate Allure reports.
Issue micronaut-java-plugins #124 🔑 Ensure proper ordering of execution status updates
The result publication mechanism has been improved to make it more robust. Some issues (incorrect status, locked elements) could appear depending on the order of the status updates, especially with the retry feature. It should now be more reliable.
Issue squash-orchestrator #408 🔑 [Premium/Ultimate] Rework log wording when license is found
Some logs about the license were reworded to avoid confusion.

Issue micronaut-java-plugins #121 🔑 [UFT_interpreter] Date format are not flexible enough
UFT tests could have the ERROR status even if they were executed correctly. This issue happened when the parser tried to calculate the execution time, more specifically when the format (based on the execution environment) was different than the standard european one (dd/MM/yyyy - HH:mm:ss). A new environment variable UFT_DATE_FORMAT has been introduced to allow the user to specify a specific format. An issue with the execution time calculation will also no longer block the interpreter, results will still be sent to SquashTM. More details can be found here.