Release Notes 7.5.17
Improvements
Analysis
The git mining step of the analysis is now much faster, especially for large repositories. File renames are still tracked, but files created as copies of other files no longer inherit the original's history.
CLI review of large C# files is faster, with unchanged results.
Code coverage
The code coverage upload API now accepts only the
ednformat used by current CLI versions. Other formats are rejected as deprecated, thesubpathandrepo-pathoptions are removed, and all uploaded coverage metrics are used in the analysis.The "Getting Started" guide for the Coverage CLI is rewritten as one step-by-step guide with copy-paste CI recipes.
Access management
Editing user access mappings is faster.
Usage data
Usage data no longer includes coverage percentages or delivery KPIs.
CLI analytics events now carry their payload once instead of twice.
Removed
CodeScene no longer mines your history for refactoring examples. Refactoring examples are therefore no longer shown in the Virtual Code Review, the delta analysis or the Performed Refactorings page, and the Latest improvements section on the dashboard lists Code Health improvements without example diffs.
Fixes
Pull request integrations
The GitHub PR checks now run when GitHub moves the base branch of a stacked PR, for example after the PR below it is merged.
PR checks no longer fail with "failed due to an internal error" when two PRs in the same repository are analyzed at almost the same time. The Git fetch is now retried once after the other Git operations on that repository finish.
Code Health analysis
Clojure: a
defwith a docstring and a data value is no longer analyzed as a function, which removes false Large Method findings on documented data vars. Code Health scores for such files may rise, and cached Clojure scores are recalculated on the next analysis, which can take longer on large Clojure codebases.PHP constructors are now checked against
constructor_max_argumentsinstead offunction_max_arguments.
Code coverage data
Deleting code coverage data through the API now also deletes the coverage files on disk.
A new coverage upload now replaces earlier uploads for the same repository and files, whichever metric was selected. Separate per-metric reports for the same files are no longer kept side by side; only the latest is kept.