Skip to content

Releases: clearlyip/code-coverage-report-action

v5.0.1

19 May 05:58
c087074
Compare
Choose a tag to compare

What's Changed

Full Changelog: v5...v5.0.1

v5.0

17 May 22:28
c087074
Compare
Choose a tag to compare

What's Changed

  • fixes #52 support cobertura class level coverage by @tm1000 in #53
  • Fixes #39 Implements Negative Difference Threshold by @tm1000 in #54
  • Add additional tests by @tm1000 in #59
  • Fixes #58 Add a flag so that only classes for which coverage changed are listed by @tm1000 in #60

Full Changelog: v4...v5.0

v4.1.1

22 Mar 01:24
Compare
Choose a tag to compare

What's Changed

  • Fixed debug aaaa still being in generated dist

Full Changelog: v4.1.0...v4.1.1

v4.1.0

20 Mar 20:23
Compare
Choose a tag to compare

What's Changed

  • Support pull_request_target event by @kuhnroyal in #50
  • Upgrade dependencies

New Contributors

Full Changelog: v4.0.1...v4.1.0

Handle single packages in cobertura files

26 Nov 07:09
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.0...v4.0.1

Adds ability to define custom markdown

01 Nov 21:35
Compare
Choose a tag to compare
  • Adds ability to define custom markdown files

Improved Baseline Reporting

26 Oct 22:16
Compare
Choose a tag to compare
  • Fixes an issue with the report showing no difference when the baseline had 0% coverage. When there is no baseline to compare with, it will output the new head coverage percentage.
  • Generate a head-coverage-only markdown report for push, schedule, and workflow_dispatch event types.
  • Upgrade dependencies
  • Add additional debug logging

Thanks to @mlafleur

Coverage drop comparison by overall coverage

05 Sep 07:19
Compare
Choose a tag to compare
  • Adds addition configuration options to facilitate calculating coverage drop by package or overall coverage.
  • negative_difference_by: Defines the scope for calculating a drop in code coverage. Possible values are overall and package . Evaluation by package is the default and represents the current behavior. When set to overall, the diff percentage is based on the total code coverage.
  • negative_difference_threshold: The percentage drop in coverage that should be allowed, in decimal form (0.05 == 5%). This sets the threshold of allowable variance in the code coverage between builds. The default is 0 (none).
  • Configure the number of retention days to apply to uploaded coverage assets.

Thanks to @mlafleur

Update Requirements for GitHub publishing

26 Sep 22:23
Compare
Choose a tag to compare

Update requirements for Github marketplace publishing.