Update Notices for Teamscale 2025.7
Teamscale 2025.7 is now available
- The Docker image
cqse/teamscale:2025.7.0is now available on Docker Hub - You can also download Teamscale as a ZIP archive here
2025.7 Deprecated the movetolastcommit query parameter in all 'External Analysis' API endpoints
The movetolastcommit parameter is no longer needed and has been deprecated to avoid confusion for all the 'External Analysis' API endpoints:
- Create a Session:
POST /api/projects/{project}/external-analysis/session - Upload External Report(s):
POST /api/projects/{project}/external-analysis/session/{sessionId}/report - Upload External Analysis Data:
POST /api/projects/{project}/external-analysis/session/{sessionId}/external-analysis-import-infos - Upload External Findings:
POST /api/projects/{project}/external-analysis/session/{sessionId}/external-findings - Upload External Metrics:
POST /api/projects/{project}/external-analysis/session/{sessionId}/external-metrics - Upload Non-code Metrics:
POST /api/projects/{project}/external-analysis/session/{sessionId}/non-code-metrics
The parameter will be completely removed for all endpoints with version 2025.9.
2025.7 Deprecated Base Configuration for Threshold Configurations
The ability to define a Base Configuration for a Threshold Configuration has been deprecated and will be completely removed with version 2025.9.
2025.7 Removed SPCop Upload Format
The SPCop upload format has been completely removed with version 2025.7.
2025.5 Removed Legacy API: Pre-Commit 2 REST API
The pre-commit 2 REST API, unused by Teamscale's own IDE plug-ins since version 9.3, has been completely removed with version 2025.5.
Action required: If you are using the API to make pre-commit requests, either update to the new /api/projects/{project}/pre-commit3 REST API or, preferably, use the command-line client for developers (teamscale-dev) to perform your requests.
2025.4 Removed feature: Timespan-based threshold configurations
The Timespan-based threshold configurations section of the "Threshold Configuration List" project option has been removed, as this functionality caused inconsistencies when combined with certain other features and was rarely used. This change does not affect the project's default threshold configuration.
2025.2 .NET 8 Required (for analysis of C# code)
Starting with version 2025.2, the Teamscale server will require .NET 8 to execute the internal analysis tools StyleCop, SonarLint and SecurityCodeScan.
Action required: In case you are not using a Docker-based deployment, please make sure to update to .NET 8 framework.
2024.9 Java 21 Required (Teamscale server application)
Starting with version 2024.9, the Teamscale server will require Java 21 to be executed.
Action required: In case you are not using a Docker-based deployment, please make sure to update the JRE used for executing Teamscale to Java 21.
2024.9 Java 21 Required (teamscale-dev)
Starting with version 2024.9, the platform-independent download (teamscale-dev.zip) of teamscale-dev will require Java 21 to be executed.
Action required: In case you are not using the self-contained platform-dependent teamscale-dev download (teamscale-dev-windows-x86_64.zip, etc.), please make sure to update the JRE used for executing teamscale-dev to Java 21.
2024.8 Disabled Legacy API: Update .NET Profiler, ADO Plugin & REST API calls
From version 2024.8 the Legacy API has been disabled by default, and we plan to completely remove it with 2025.1 (or later).
Action required: Make sure you update the Teamscale .NET Profiler, Teamscale Plugin for Azure Dev Ops or scripts that interact with Teamscale's Legacy REST API to their newest versions.
To temporarily re-enable the Legacy API (in case you cannot upgrade a part of your setup yet), you can set the system property com.teamscale.legacy-api.enabled to true.
Teamscale will show a warning banner to administrators if usages of the Legacy API have been detected since the last instance restart. You will find the used legacy services in the System -> Service Log view.
Re-Analysis when Upgrading
- When updating from 2025.7.x, drop-in.
- When updating from 2025.6.x or earlier, a full re-analysis via backup is required.
What's New for Teamscale 2025.7
Quality Control: Reports
Section Title Slide
Users can now include a subtitle or a multiline title in Section Title slides, providing more flexibility when creating reports.
Assessment Trend Slide
The Assessment Trend Slide has been enhanced to display percentage values and project baselines for each assessment on the chart, allowing for greater insight and flexibility.
Web Interface
- Architecture findings now display the comment provided by the architecture modeler for both the source and target components when hovering over the
?symbol. This improvement eases the understanding of architecture violation findings by giving developers context and guidance on resolution.
New Checks
- New "Empty test case" check for Natural Language Tests.
Static Analysis
GitLab SAST Rules Integration
The GitLab SAST ruleset in Teamscale has been updated to version 2.8.4, incorporating new rules and several fixes to reduce false positives.
Enhanced Clang-tidy Support (C/C++/Obj-C)
Teamscale now allows the specification of target triples and additional settings, like framework paths and ARC options, for Clang-tidy in C, C++, and Objective-C analysis profiles, improving analysis accuracy and reducing parser errors; these settings can be configured in the Advanced options of the analysis profile.
For more details, please refer to our documentation on defining the target triple and additional arguments.
IntelliJ Plugin
Developers can now mark findings as false positive or tolerated directly within IntelliJ's Problems Tab, utilizing IntelliJ's quick-fix mechanism. This enhancement improves usability by allowing these actions without leaving the tab.
Administration & Operation
External Storage Backend
Teamscale now supports the simultaneous use of timestamp-based and revision-based uploads in external storage. This enhancement dynamically determines the upload type based on the provided parameters, ensuring consistency with legacy behavior while facilitating seamless integration.