Patch Releases for Teamscale 2025.8
Version 2025.8.6
Fixes
- Test Selection: Querying tests failed with an exception if nothing was matched
- "Send Test Mail" button did not work unless settings were saved
- Color-blind mode did not work in the Code view for test coverage annotations
- False positives for "Unused variable or parameter" check for Java
- Worker log was filled with "Semgrep execution failed" messages
- Bad request error due to "Illegal header name" in some cases
- False positives for "Unused variable" check for C++ when using lock guard RAII pattern
- IDE plugins: "Open in Browser" generated a URL that did not work with Teamscale 2025.7 and later
- False positives for "Data Structure Alignment" check for C++ static members
Version 2025.8.5
Fixes
- JLink reports with empty file names could not be parsed
- False positives for "Unused variable" check for Kotlin when using
throwsin combination with the Elvis operator - Certain events were not listed in audit logs
- Too many role changes were logged when using Prometheus monitoring
- False positives for "A compatible declaration shall be visible with external linkage" check for Objective-C
- False positives for "Empty blocks" check for C++ when
[[nodiscard]]was used in constructors
Improvements
- Descriptions for bandit checks were improved
Version 2025.8.4
Fixes
- Reports: Slide number enablement was not transferred to a copied report
- Too many external findings were resolved when using code scopes
- When external storage backends were enabled, using the same session to upload multiple reports sometimes failed with a 404 response
StringIndexOutOfBoundsExceptionin "Avoid unused private methods (Java)" checkNullPointerExceptioninRaexFindingsSynchronizer- Legacy URLs were not redirected correctly
- Tasks: Code snippets were added with the wrong timestamp when time travel was not active
Version 2025.8.3
Fixes
- SAML login did not work due to a CSRF validation error
- Code scope paths could not be selected for Metrics of Threshold groups
- False positives for "Class named like Exception should extend Exception or subclass" check
- ABAPLint was falsely executed on DDIC objects
- Swift distributed actors were not parsed correctly
- GitHub Issue Tracker: GitHub issues were not imported when the "Import only Items Changed After" option was set to
all items - Critical change badges did not consider files with non-method changes or trivial method changes
- Newlines were not preserved when reading files with
teamscale-dev - False positives for "Types shall be explicitly specified" check for C when the
_Atomickeyword was used
Version 2025.8.2
sha256: f61a7711f081a9d6f49b0d7992bd012b2563b8bef50f0c95b60647a0dfce98df
Fixes
- Trailing commas in list-style text inputs were automatically removed when editing analysis profiles and projects
- LCOV report could not be parsed because of a
NaNvalue - Processing of Bullseye C++ coverage failed for some
switch-caseconstructs BugTrackerExceptionwas sometimes thrown inJiraIssueUpdatePostAnalysisTriggerwhen a multi-connector project had a non-Jira issue connector- False positives for "Unreachable Code" check for Javascript/Typescript for usages of
is keyoftype guard - False positives for "Dead Store Analysis" check for C++ for usages of concepts
- External storage backend could not be created if the external account's URL ended with a trailing slash
- External storage backend configuration conflicted with S3Connector
- Abap import logged wrong warning "Last SCOV collection happened more than one hour ago, SCOV likely became inactive."
S3ChangeRetrieverdid not reschedule after rate-limiting errors- Analysis was stuck in rollback loop after extensive Git rebasing
Improvements
- Introduced a new feature toggle for disabling the fallback parsing heuristic
Version 2025.8.1
sha256: ce559113dd24e7da119d2bbbdbc3e942ad4919d56a2d7fe4623e85ecfe740b4f
Fixes
- SAP NetWeaver 7.40 systems: ABAPLint was called with the wrong ABAP version
- Quality Control > Reports view: Creator name was overflowing the Action column on narrow screens
- GitHub: Links to the file coverage comparison view in the Teamscale > Test Coverage check runs were broken
- When using multiple S3 connectors, the "last updated" timestamp of all partitions was updated on new uploads
- Bullseye Coverage: Processing of Bullseye C++ coverage failed and caused long-running workers
- False positives for "Unreachable code after exit statement" check for Kotlin when using elvis operators
- False positives for "Non-void function should return a value" check for C++ when using co-routines
- Delta > Findings Churn view: Previous state of the findings filter was not restored when using the browser's back button
- Binary size metrics were computed incorrectly after force pushes in some cases
StackOverflowErrorin Simulink data type propagation engine- Deleted branches were not available in the branch chooser in some cases
DataFlowFindingsSynchronizerfailed when using computedgotofor C++
Improvements
- Maximum S3 change retriever blocking time is now configurable via the system property
com.teamscale.aws.s3.max_block_time_minutes - "Hard-coded password" check description was improved
Version 2025.8.0
Bug Fixes
- 2025.8.0 contains all fixes from previous versions released on and before October 28th, 2025
- For brevity, only new features are included in the changelog
sha256: 25bace69990813f237b4f55208526fa2954313bc494575cd50db0fe5e4861c26