--- url: /changelog/v2025.3.x/patch-releases.md --- # Patch Releases for Teamscale 2025.3 ## Version 2025.3.17 ### Fixes * False positives for "Avoid usage of implicit int" check when using `typedef volatile struct` for C/C++ ### Improvements * Pull requests that have no relevant test gap analysis changes or no coverable lines will now get a positive vote *** ## Version 2025.3.16 ### Fixes * Cleanup of pending GitHub check runs failed with a `NullPointerException` *** ## Version 2025.3.15 ### Fixes * Branches of cross-repository merge requests were not fetched under certain circumstances *** ## Version 2025.3.14 ::: details Security Improvements This version contains security improvements. If possible, please update to at least this version. ::: ### Fixes * *Dashboards*: Opening method history links via architecture paths did not scroll to the method in the *Code* view * Security: Potential CSRF vulnerability when rendering commit messages *** ## Version 2025.3.13 ### Fixes * Some delta analysis services returned the wrong data when a selected path was a prefix of another path * Number of contributors for ABAP systems included committers of transported changes * `NullPointerException` in null-pointer analysis for C++ when using the "direct initialization" syntax * IntelliJ plugin: Read access errors when fetching findings from selected file ### Improvements * Improved memory consumption when processing issue references *** ## Version 2025.3.12 ### Fixes * Code view: Missing warning about outdated coverage * Azure DevOps: Pull requests with configured branch policies could not be voted on in some cases * Visual Studio plugin: Misconfigurations in `.teamscale.toml` file could lead to `NullPointerException` when flagging findings *** ## Version 2025.3.11 ### Fixes * *Reports*: Pressing "Delete" while editing a callout text deleted the callout * *Metric Table* widget opened the trend dialog for the wrong path in some cases * Coverage could be matched to the wrong file when multiple files in a JaCoCo report had the same file name * "Ignore Methods matching" check option for "Method Length" check did not work for preprocessed languages * Branches for cross repository merge requests could not be fetched in some cases * "Content exclude" option was not considered in pre-commit analysis for ABAP ### Improvements * Visual Studio Code plugin: Long running background operations (e.g. pre-commit analysis) now show progress notification *** ## Version 2025.3.10 ### Fixes * Server settings validation failed for option "ABAP SNC service library path" when no SAP connectors were set * Eclipse plugin: `NullPointerException` when third-party plugins shipped a non-compliant `javax.annotations` package * Comparisons such as the broken clone comparison showed an assertion error if the token-based comparison mode had previously been enabled *** ## Version 2025.3.9 ### Fixes * Visual Studio Code plugin: UI froze when pre-commit analysis was running in the background * PL/SQL parser error when using compound triggers or `RUN` as an identifier * *Tasks*: Avatars could be distorted when task titles were long * Clone finding comparison showed `undefined is not an object` error if the token-based comparison mode had previously been enabled *** ## Version 2025.3.8 ### Fixes * *Merge Request* view: Metrics delta table did not display any data, in case findings were tolerated on the merge request's source branch. * Bitbucket Data Center: Emojis in Teamscale's inline diff comments were sometimes not rendered correctly * Reporting: Incorrect finding ID on "Finding Detail" slide led to infinite render loops * TFVC: File renames in merges were not recognized correctly * Visual Studio Code plugin: Extension failed if path to extension directory contained spaces * Dashboard: Guideline Summary Table widget did not show data for MISRA C 2012 * GitLab and Azure DevOps: Line comments were duplicated if they contained many aggregated findings * Teamscale Upload tool: External generic findings were not uploaded * Visual Studio plugin: *Findings* view did not update after tolerating or flagging a finding ### Improvements * Improved description for check Forbidden Standard I/O-Functions * AWS client region can be set using system property `com.teamscale.aws.region` *** ## Version 2025.3.7 ### Fixes * IntelliJ plugin: Double clicking a finding in the *Findings* tool window did not open it in an editor * Deleting data directly from S3 did not remove all analyzed metric paths * Worker logs regarding architectures did not specify the architecture name * False positives for Javascript naming convention check * Intellij plugin: Help text for `teamscale-dev` `--user` and `--accesskey` option was shown twice * GitHub integration: Inconsistent check details when ignoring yellow findings for voting * False positives for "Post-Operator in return statement" check * Intellij plugin: "Enable Automatic Pre-Commit Analysis" and "Show Assessment in Editor Gutter" toggles in the Teamscale menu did not show a checkmark when enabled * Simulink datatypes were propogated as `Unknown` when using "Vector Concatenate" blocks *** ## Version 2025.3.6 ### Fixes * Reporting: Difference indicators on finding details compare slides were off when changing the font size * Reporting: Highlighting identifiers on finding details slides was not possible * Reporting: Creating new reports failed if there were multiple thresholds with the same name * Reporting: Thresholds could not be selected during report creation in Firefox * Reporting: The TGA slide partition selector was reset too frequently * Projects with Gitlab Requirements Connector could not be created * *Metrics* perspective: Directory table entries containing `-src-` in their names were truncated incorrectly * External revision lookup was too slow when using an external storage backend * Findings *Filter Options*: Guideline filter was no longer shown if filter did not match any findings * Indentations of role assignment table entries and of the assignment dropdown were inconsistent * *Code Compare* view: Changes in broken clones were not highlighted ### Improvements * External Upload Processing: Reduced the amount of memory needed to process reports from artifact repositories such as S3 or Artifactory *** ## Version 2025.3.5 ### Fixes * Uploads to S3 external storages targeting the same commit and partition were not processed * Sonarlint check descriptions contained escaped symbols * IntelliJ plug-in: Broken link to plug-in changelog on JetBrains Marketplace * False positives for the naming convention check for MATLAB * `Cannot read properties of undefined` error occurred when clicking on a Simulink block * False positives for `Prefix is current class` check for ABAPLint ### Improvements * Eclipse plug-in: "Teamscale Not Enabled for Project" notifications now offer to open project preferences *** ## Version 2025.3.4 ### Fixes * `PatternSyntaxException` in `GitHubChangeRetriever` when debug dumping was enabled and branches with special characters were analyzed * `IllegalArgumentException` in `ExternalAnalysisResultsPersister` when test names in JUnit reports had trailing spaces * False positives for "PHPStan: class.notFound" check when using heredocs * *System Information* view: List of active committers was not scrollable * Views sporadically broke with the error `Cannot read properties of null (reading appendChild)` * Editing a paused project unpaused it * Branch selector had a dropdown icon instead of "x" icon for deleting current selection * False positives for "Endif directive comment" check ### Improvements * *Issue-based Metric Treemap* and *Method-based Treemap* widgets now support CSV download *** ## Version 2025.3.3 ### Fixes * *Findings* perspective: Missing "Clear" button in the "Guideline" filter dropdown * `net::ERR_CONTENT_DECODING_FAILED` error in rare cases * External findings were not resolved after uploading a new external report in some cases * Datatype was not propagated from inports to Bus selector * Issue queries: `membersOf` function did not respect the users' full name * Placeholder text was shown in blue color in some places * Duplicate tables were sometimes added to issues in Jira Cloud ### Improvements * New server options to limit how many pre-commit branches are retained for how long (per user) * When the `repository` parameter for a jQAssistant upload is set, it is now expected as a prefix for matched file paths *** ## Version 2025.3.2 ### Fixes * Worker log messages did not contain the architecture they were referring to * Summary for "Comment Completeness Assessment" contained entries of deleted files * Images in documentation were no longer zoomable * PHPStan did not reliably detect PHP version constraint from `composer.json` file * Voting repeatedly on merge requests failed for projects with issue or requirement connectors * Azure DevOps: Duplicate pull request comments for architecture findings * False positives for "Avoid unused private methods" checks for C# * False positives for "Unused variable or parameter" check for out parameters in C# * False positives for "Incorrect JavaDoc usage" check when using Java annotations in comments * `NullPointerException` when receiving webhooks in case there were unconfigured projects * "Code Change" links for alerts in *Delta* perspective pointed to wrong commits * `GitLabMergeRequestUpdateTrigger` failures in case the project ID was used in the project configuration instead of the repository name * False positives for "Non-empty switch clauses have to be terminated unconditionally" check for C/C++ * "Start date" in "Branching Configuration" was not optional * Analysis profile options for "Comment Style" check did not work * *Code* view: Expanding/Collapsing a macro while browsing search results always reset the view to the first search result ### Improvements * Documentation: Added missing redirects to "Integrations/jenkins-plugin" *** ## Version 2025.3.1 ### Fixes * Documentation: Old link of "Uploading External Analysis Data" page lead to 404 * Identical ABAPLint findings on same line but different character offsets were missing * Generics in Python type hints were not parsed correctly * Default tools were not enabled when adding a new language in an analysis profile * Lazy initialized attributes in Kotlin were not parsed correctly * Saving external credentials without validation did not work in some cases * False positives for "Do not access internal class members" check in Python when accessing magic methods * False positives for "Unused variable or parameter" check in C/C++ * TGA badge did not have the correct colors * Cppcheck did not terminate in some cases * Selecting a date in the calendar popup did not update the date in Safari in some cases * Simulink: Clone siblings were shown vertically to each other instead of horizontally * Multiple GitHub pull requests with the same source branch caused Teamscale to repeatedly update the same check runs indefinitely in some cases * *Tasks* view: Findings links incorrectly included last selected time travel * *Issue-based Metric Treemap* widget did not respect "Exclude non-referenced files" parameter * *Delta* perspective: Link to comparison for changed files had commits swapped for merge deltas * C#: Parser error when overriding `true` and `false` operators * `StackOverflowError` in "Nonsensical Binary Operation" check when checking large string concatenations * Scanner error in Transact-SQL when using curly braces * *Access Keys* view was not centered * Analysis progress bars had no progress indicators in the *Analysis Progress* table of the *System Execution* view * GitHub check runs did not state the reason for a result in the check run overview * Cleanup of GitHub check runs did not work in some cases * Incorrect findings for architecture violations * Semgrep could not execute under rare circumstances * `NullPointerException` in some cases when opening the code perspective * C++: `complex` was incorrectly parsed as a keyword * Parser errors for C++ when using casts *** ## Version 2025.3.0 ::: details Bug Fixes * 2025.3.0 contains all fixes from previous versions released on and before April 1st, 2025 * For brevity, only new features are included in the changelog :::