Patch Releases for Teamscale 2026.1
Version 2026.1.9
Fixes
- External uploads were not sorted properly in the External Upload page
NullPointerExceptionduring coverage integration in rare cases- Timeout for importing a backup from another instance was too short
- False positives for "New exception is created but not thrown" check in Java when using throw in a switch statement
- ABAP: Field-symbols were incorrectly interpreted as HTML tags, causing them to be rendered as strikethrough
- Merge Request Details view showed outdated information when processing squashed or rebased commits
- Overlapping enablement of metric and critical change badges between projects was not detected
- Simulink: Datatype propagation did not work correctly when a library was included multiple times
Improvements
- Cppcheck: Parsing issues are now logged with precise location information
- Improved C/C++/Objective-C/++ scanner performance for some code patterns
Version 2026.1.8
Fixes
- Dashboards: Widgets were broken when creating dashboards from templates
- Coverage sources were reset when changing the visibility of a path in a widget title
- The "Coverage of Changes" section in the Merge Request Detail view considered coverage from previous commits if no coverage data had been uploaded for the head commit
- False positives for "Classes should not depend on an excessive number of classes (aka Monster Class) (java:S6539)" check
- Instance Comparison: File content differences were always shown for Simulink files, even when they were identical
- C/C++: Comments after preprocessor directives were not parsed correctly in some cases
Version 2026.1.7
Fixes
- Webhooks were sent before Teamscale voted
- Dashboard: Color pickers did not store new colors
- False positives for "Null pointer dereference" check in C# when using the null conditional operator in
string.IsNullOrEmpty - Navigating between the method history view and the code view resulted in a "Bad Request" error
- Synchronization of ignore rules from Teamscale to JFrog failed with a "Bad Request" error
- Tasks: Links to findings did not work in task edit mode
- Code scope configuration was imported incorrectly if configuration lines ended with a comma
Improvements
- The "Upload Commit Details" dialog now explains that displayed data covers all partitions when multiple partitions are present
Version 2026.1.6
Fixes
- False negatives for "Catch of generic exception" check when exceptions were annotated
- Cppcheck Premium 25.8.3 Windows binaries reported file paths with Unix-style forward-slash separator
- Clang-Tidy findings were missing when Teamscale ran in a Docker environment
- SwiftLint:
IllegalArgumentExceptionwhen parsing results - Duplicate entries and incorrect role assignments were shown in the Global Role Assignments view when users shared multiple groups
- Merge request details were not shown in some cases
- Simulink:
DatatypesinBus Selectorblocks could not be resolved whenAliastypes were used - Objective-C: Instance method declaration lines were considered coverable in some cases
NullPointerExceptioninContentIndexSynchronizerwhile resolving includes
Improvements
- Improved error handling for backup imports from remote Teamscale instances
- Reduced memory consumption when processing many uploads during a backup import
Version 2026.1.5
Fixes
- Visual Studio Code plugin: Opening a file that was excluded from the Teamscale analysis resulted in an error
IssueSynchronizersfailed when encountering an invalid link- JavaScript: Clones with template literals were not detected correctly
- Page state was lost after confirming the "Do you really want to leave the page?" dialog
- Excluded findings were not shown in the Activity view for approval commits
- During backup import, it was possible to log in with outdated credentials of local users
- GitHub Enterprise could not be configured due to a
NullPointerException - False positives for "Usage of Abs Block" check for Simulink when setting the block parameter "Saturate on integer overflow"
Improvements
- "Hard-coded password" check: Added support for detecting hard-coded secrets
Version 2026.1.4
Fixes
- Superfluous error logs were shown for Bandit when using code scopes
- Stale project options were shown after updating them
- Instance Comparison:
ClassCastExceptionwhen comparing ABAP projects - Worker Log did not show the number of errors and warnings
IssueTrackerSynchronizercould fail due to a missing scheduling commit- Uploading findings via the
/external-findingsendpoint failed when external storage was enabled - Cleaning up outdated GitHub check runs failed for repository names with uppercase letters
- False positives for "Missing virtual destructor" check in C++ for stack-only classes with deleted
newoperators - False positives for "Check usage of unconditional transitions in flow charts Correctness" check for Simulink
- False positives for "Check usage of Signal Routing blocks" check for Simulink
Version 2026.1.3
Fixes
- Kubernetes: Invalid YAML files sometimes led to a
ClassCastException - Documented configuration for using the Windows trust store did not work for recent JVMs
- Groups created by importing teams from GitHub were missing the organization name
- Go: Tuple return types were not correctly parsed
- External analysis data was not correctly deleted during history analysis
- Bitbucket Data Center: Code Insight report status was always
PASSEDand did not match the Teamscale vote status - Post-poned votes were not cleared from the index after a merge request was merged
- Code Compare view broke with error
Must insert in ascending order! - AI resolution failed when fixing a finding required adding extra lines of code
- Polarion: No specification items were imported when a custom field was defined multiple times
golangci-lint: Configured options were not passed correctly- False positives for "Don't use string in Matlab Function Blocks" Simulink check when function calls were used
- False positives for "Unauthorized Access Control Object" ABAP check when
#MANDATORYannotation was used
Improvements
- Improved GitHub connector validation speed for apps having access to a lot of repositories
- Renamed "Test Coverage" section in the merge request detail view to "Coverage of Changes"
- Improved Maven plugin documentation
Version 2026.1.2
Fixes
- Postponed rollbacks were not cleared correctly after execution
- Selecting an item in a filtered checkbox list selected the wrong item
- User selector search box was occluded in the Role Assignment view
- Data in different external upload paths referencing the same commit were not merged
- Archived reports had the wrong file name when downloaded
- No findings were shown in the treemap when a code scope was selected
ClassCastExceptionin metrics handling for ABAP projects- After external uploads, redundant revision lookups were performed in some cases
- Comments in anonymized code were not anonymized correctly
- Updates to existing cross-repository pull requests were not processed when no other branch changes occurred
NullPointerExceptionin plausibility check during path matching when processing "Testwise Coverage" reportsEOLtokens were not fully cleared from the display when switching between token and AST representations- Teamscale comments in Azure DevOps pull requests could not be displayed in Visual Studio
Version 2026.1.1
Fixes
- Reports perspective: Slide previews did not automatically scroll into view when switching slides
- Reports perspective: Banner on the left side of slides did not expand to the full slide height in Safari
- Service to force S3 full scan did not work when feature toggle
com.teamscale.external-storage.disable-user-configurationwas enabled - ABAP code in check descriptions was not highlighted correctly
DataFlowFindingsSynchronizerfailed for C# when detecting infinite loops inside a lambda- Errors during backup import due to missing check descriptions for "Cppcheck Report Uploads (External)" tool
NullPointerExceptioninInconsistentCloneChangeAlerter- False negatives for "Annotation in JUnit test class missing" check for Java
- "Metrics Trend Chart" widget parameter validation could fail even if at least one color was selected for each metric
- Button to add a new dashboard on the Dashboard perspective was shown even if no projects existed
- GitHub: Periodical sync of GitHub teams to Teamscale group assignments did not work
- False positives for ESLint checks ("no-shadow", "no-redeclare", "no-unused-vars") for TypeScript code
- Legend colors in trend charts on the Start perspective were swapped
- Dashboards created from templates were created for the wrong project in some cases
- False positives for "Use of enclosing braces, partial array initialization, multiple initialization of array elements" check for C/C++ when using partial array initialization with
{NULL}or{nullptr} - False positives for "Methods should not be defined in a header file" check for C++/Objective-C/++ when using
__inline__ - Trend chart failed to render for the ABAP "Creation Date" metric
- Extended code snippets in the Finding Details view did not use the available height in some cases
- Treemap colors were inconsistent for metrics with a fixed set of values (e.g. languages) when some values were not present in the project
- "No testwise coverage" was shown when coverage was actually present in some cases
- Jira connector did not accept valid URLs in some cases
- False positives for "Switch statements should not contain unexpected constructs" check for C/C++ when all conditional branches had exit statements
Improvements
- Reduced memory consumption in
FindingsTracker - Improved slow initial trigger execution for huge projects
- Polling interval for external storage backends can now be configured with the system flag
com.teamscale.external-storage.polling-interval - Improved check description for "No call to external form routines" check
Version 2026.1.0
Bug Fixes
- 2026.1.0 contains all fixes from previous versions released on and before January 20th, 2026
- For brevity, only new features are included in the changelog