Release Notes and Deprecations
Release Notes
You can access the Release Notes of SquashTM Web App and its plugins as well as SquashTM Orchestrator by navigating with the left panel.
Deprecations
| Release Estimated date |
Deprecated feature |
|---|---|
| Squash TM 8.0 / Squash Orchestrator 2024‑10 Oct 2024 |
Allure report Squash Orchestrator stops generating Allure reports by default. The generation is reactivable via configuration, using OPENTF_ALLURE_ENABLED environment variable: see the OpenTestFactory documentation for details.See announcement. |
| Squash Orchestrator 2024‑11 Nov 2024 |
Plugin for Jenkins The Plugin for Jenkins is deprecated. It will not support the latest Squash Orchestrator features. Jenkins will have to use opentf-ctl as described in the OpenTestFactory documentation. |
| N/A Dec 2024 |
squashtest/squash-tm Docker imageOn 2024-12-31, we will stop publishing any squashtest/squash-tm Docker image. Only squashtest/squash will be available (this is the same image, but signed).See announcement. |
| Squash TM 9.0 / Squash Orchestrator 2025‑01 Feb 2025 |
Jira authentication via OAuth 1A Jira authentication via OAuth 1A will not be supported anymore, the OAuth 2 protocol will have to be used. See announcement. |
Import of test cases in .zip formatTest case import using a Zip file will not be possible. Import will have to be performed using the more comprehensive Excel format. See announcement. |
|
Export of test cases in .csv formatTest cases will not be exportable anymore as CSV files. Export will have to be performed using the more comprehensive Excel format. See announcement. |
|
| Squash TM 10.0 May 2025 |
Supported databases Support for PostgreSQL 13 and 14 will be discontinued, PostgreSQL 15 or later will be required. Support for MariaDB 10.6 will be discontinued, MariaDB 10.7 or later will be required. |
| Java version Squash TM 10.0 will require Java 21. |
|
| Basic authentication for REST API Basic authentication for REST API will be disallowed by default. It will be reactivable via the squash.rest-api.disallow-basic-authentication configuration parameter.See announcement. |
|
| Jira Requirements plugin Jira Requirements plugin will no longer be distributed. Requirement synchronization from Jira must be done using the more comprehensive Xsquash4Jira plugin. |
|
| Squash TM 11.0 August 2025 |
RTC Bugtracker Squash support of RTC (Rational Team Concert) Bugtracker will be dropped. |
| Allure report Squash support of Allure reports will be dropped. No Allure report will be creatable anymore. See announcement. |
|
| Docker image - Deprecated MySQL/MariaDB specific environment variables Deprecated since Squash TM 5.0, the following environment variables will be definitely abandoned:
|
|
| H2 The H2 DBMS, which allows for a quick discovering of Squash TM, but should not be used in production, will no longer be supported. People wishing to easily discover Squash TM can do so by using the Docker image or our trial offers. |
|
| SquashTM 12.0 November 2025 |
Plugin for Jenkins The Plugin for Jenkins will not be released anymore. Jenkins will have to use opentf-ctl as described in the OpenTestFactory documentation. |
| Docker Image - Upgrade Warning: To migrate from Squash TM 8.1 (or earlier) to SquashTM 12.0.0, you must go through an intermediate version Squash TM 9.X. Direct upgrade is not supported. |
|
| SquashTM 15.0 August 2026 |
Tags from custom templates for campaign and iteration reports prior to Squash TM 11 Custom templates for campaign and iteration reports, created from a default template before Squash TM 11, contain tags that will no longer be supported. These tags will be removed. |
| TBD Mid 2026 |
Basic authentication for REST API Basic authentication for REST API will not be supported anymore. See announcement. |
| Jira 9.X support Jira 9.X support will cease with the end of support for this version by Atlassian. |
|
| SquashTM 21.0 February 2028 |
Very old passwords Starting with Squash TM 1.19 (released at the end of 2018), passwords are hashed using bcrypt instead of SHA-1, which has been found to be insecure. Users who have not changed their password since this upgrade need to either:
|