---
url: /changelog/v2025.7.x/patch-releases.md
---

# Patch Releases for Teamscale 2025.7

## Version 2025.7.16

### Fixes

* Service to list local Git clone directories could not handle versioned clone directories

***

## Version 2025.7.15

### Fixes

* *Parser* and *Interaction* log were empty with default logging configuration

***

## Version 2025.7.14

### Fixes

* HANA SQLScript `?` operator was not supported
* False positives for "Methods should not be defined in a header file" check for C/C++ `constexpr` functions

***

## Version 2025.7.13

### Fixes

* 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.7.12

### Fixes

* 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

***

## Version 2025.7.11

### Fixes

* Legacy URLs were not redirected correctly
* Code snippets were added to tasks with the wrong timestamp when time travel was not active

***

## Version 2025.7.10

### Fixes

* 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 `_Atomic` keyword was used

***

## Version 2025.7.9

### Fixes

* LCOV report could not be parsed because of a `NaN` value
* Processing of Bullseye C++ coverage failed for some `switch`-`case` constructs
* `BugTrackerException` was sometimes thrown in `JiraIssueUpdatePostAnalysisTrigger` when a multi-connector project had a non-Jira issue connector
* False positives for "Unreachable Code" check for Javascript/Typescript for usages of `is keyof` type 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."
* `S3ChangeRetriever` did 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.7.8

### Fixes

* 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 were 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
* `StackOverflowError` in Simulink data type propagation engine
* Deleted branches were not available in the branch chooser in some cases
* `DataFlowFindingsSynchronizer` failed when using computed `goto` for 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.7.7

### Fixes

* Opening files in the *Metrics* perspective could fail with an `AssertionError` in some cases
* Dataflow analysis did not correctly parse complex Java annotations in generic types
* Documentation: Visual Studio Code extension page contained invalid Visual Studio Marketplace download link
* `CREATE VIEW` with alias was not parsed correctly for PL/SQL
* *Projects* view: "Updated" column was not updated when changing the project configuration in some cases
* Bitbucket Data Center: `BitbucketServerChangeRetriever` was not rescheduled in case of rate limiting errors

### Improvements

* Prometheus metric for project connector status now includes all statuses

***

## Version 2025.7.6

### Fixes

* New commits from an artifact store were not correctly added to the history
* Data returned from the server got corrupted in some cases when terminating HTTPS in Teamscale
* C/C++: `//` in URLs used inside preprocessor directives was always scanned as comment
* False positives for "Avoid unused private methods" check for Java when using `@MethodSource` annotations
* Simulink: `NullPointerException` when resolving data types
* Too strict code scope validation when creating new projects

### Improvements

* Improved loading times of *Global Role Assignments* view

***

## Version 2025.7.5

### Fixes

* False positives for "Dead Store Analysis" check for C++ concepts
* False positives for "Classes should not depend on an excessive number of classes (aka Monster Class) (java:S6539)" check for Java enums
* AssertJ's `withMessage` function was not recognized as an assertions
* False positives for `assertEquals` check with same arguments
* False positives for “Unreachable code after exit statement” check for Typescript near `keyof` operator
* After opening a *Quality Report* in edit mode, the slides of the report were slightly outdated in some cases
* Go functions/methods were not always parsed correctly

***

## Version 2025.7.4

### Fixes

* False positives for "Change the assertion arguments to not compare dissimilar types" check for types containing dots
* False positives for "Test further the exception raised by this `assertThatThrownBy` call" check within lambdas
* Errors in data flow analysis of C# local functions with tuple return types
* When upgrading Teamscale, "A compatible declaration shall be visible with external linkage" check was falsely removed from analysis profiles containing C
* Generic Go functions were not parsed correctly
* *Reports*: "Finding Details" slide did not scroll to the finding when "Show introduction/removal diff" was enabled
* *Merge Requests*: *Critical Changes* section included files and methods that were not changed within the merge request in some cases

***

## Version 2025.7.3

### Fixes

* Backup import failed for projects with S3 connectors
* Project scheduling failed with error "Can't set newer commit as parent of older commit" in some cases
* False negatives for "Avoid creating SimpleDateFormat objects without specifying the Locale" check for Java when using star imports
* `NullPointerException` in "String Interpolation" check when using `permits` as identifier
* golangci-lint was not working if the home directory was not writable
* False positives for "Unreachable Code" check for Go `switch` statement
* Anonymous blocks in Go were not parsed correctly
* Go method was not parsed correctly when `interface{}` type was used in signature
* Go built-in functions were not parsed correctly
* Very high count of log messages resulted in `OutOfMemoryError`
* When importing compilation databases, Teamscale did not resolve absolute include paths against the code directory on the build server
* `DataFlowSynchronizer` error when trying to construct CFG for C++ constructor
* False positives for Naming Convention check for C/C++ `const` `struct` members
* Taint Analysis findings did not disappear when code snippets in ABAP were commented-out
* False positives for "Unused variable or parameter" check when using GTEST tracing macros
* False positives for "Forbidden Literals" check for ABAP

### Improvements

* Improved performance of "JWT should be signed and verified with strong cipher algorithms (java:S5659)" check

***

## Version 2025.7.2

### Fixes

* Overlapping headlines in *Project Edit* view for instances without dashboard templates
* JavaScript attribute functions called `get`, `set`, `static`, or `async` were not parsed correctly
* "Show coverage" toggle was not available in *Broken Clone* view
* ABAP parser failed on string templates ending with backslash
* Projects with *Jira as Requirement Management Tool* connectors could not be edited or imported from older releases after applying the previous patch version
* False positives for "Unreachable code after exit statement" check for Objective-C when using lambdas
* Double scrollbar was displayed in the Simulink block view
* *API Reference*: Wrong description for query parameter "projectId" for `api/sap-system-id-by-project`

### Improvements

* Improved performance when fetching the resource history of a file when Code Review Findings were turned on
* Visual Studio Code plugin: Improved error logging when invalid JSON was returned for Teamscale precommit request
* SAP integration documentation now describes compatibility with git-based ABAP environments

***

## Version 2025.7.1

### Fixes

* *Reports* view: Popup contents overflowed their containers in Safari
* `AssertionError` in `TypeIndexSynchronizer` in some cases when resolving JavaScript dependencies
* Backups with Jira projects could no longer be imported from old releases after applying previous patch version

### Improvements

* Improved URI placeholder for GitLab in *External Accounts* dialog

***

## Version 2025.7.0

::: details   Bug Fixes

* 2025.7.0 contains all fixes from previous versions released on and before September 16th, 2025
* For brevity, only new features are included in the changelog
  :::
