Skip to content

Releases: greguintow/jest-coverage-comment

0.1.17

Choose a tag to compare

@greguintow greguintow released this 21 Aug 14:47
0e307ba
  • Run the action on Node 24 (runs.using: node24)
  • Parse Vitest 5 JUnit reports, including high-precision times and unhandled-error suites
  • Show file-level Vitest JSON failures and link to source from Vitest stack traces
  • Support absolute file paths on Windows runners

0.0.16

Choose a tag to compare

@greguintow greguintow released this 24 Jan 22:41

Fix where to show coverage is missing

0.1.15

Choose a tag to compare

@greguintow greguintow released this 20 Jan 20:44

Show where the coverage is missing

0.1.14

Choose a tag to compare

@greguintow greguintow released this 17 Jan 03:34
  • Fix coverage checking if was lower than required coverage to be successful instead of greater or equal

Full Changelog: 0.1.13...0.1.14

0.1.13

Choose a tag to compare

@greguintow greguintow released this 17 Jan 03:25
  • Make coverage average of lines, branches, statements and functions
  • Add required-coverage input to say when it's not reaching the desired coverage, 100 by default

Full Changelog: 0.1.12...0.1.13

0.1.12

Choose a tag to compare

@greguintow greguintow released this 29 Apr 07:12

Highlights

  • Support vitest json test report to show failed tests messages

Full Changelog: 0.1.11...0.1.12

Fix order of reports

Choose a tag to compare

@greguintow greguintow released this 03 Apr 17:17
0.1.11

fix: order of the report

Fix support single junit file

Choose a tag to compare

@greguintow greguintow released this 03 Apr 17:02
0.1.10

fix: not adding test report for a single junit file

0.1.9

Choose a tag to compare

@greguintow greguintow released this 30 Mar 23:57

Use node 20

0.1.8

Choose a tag to compare

@greguintow greguintow released this 23 Jan 22:44

Full Changelog: 0.1.7...0.1.8