Skip to content

Releases: NasAmin/trx-parser

v0.6.0 - upgrade to node20

19 Apr 22:54
d34de96
Compare
Choose a tag to compare
  • Contains dependabot version updates and security fixes
  • Fixes #301 via #304 and #305 -- Upgrades the action to node20.

Full Changelog: v0.5.0...v0.6.0

What's Changed

New Contributors

Fix xml parsing issues

20 Aug 14:01
818ff78
Compare
Choose a tag to compare

What's Changed

  • Fix xml parsing issues for nested multiline string nodes by @NasAmin in #293

Full Changelog: v0.4.0...v0.5.0

Thanks to @marcwittke for reporting this.

Security Fixes

03 Aug 20:34
6daa816
Compare
Choose a tag to compare

Dependabot updates

⚠️ This release breaks failed tests reporting. Stack trace and error message aren't reported. Please use v0.5.0 instead ⚠️

Security patches by dependabot

23 Jan 17:00
Compare
Choose a tag to compare
  • Security patches by dependabot and generate package updates to newer versions
  • Fixes #231
    • Adds a new options REPORT_PREFIX input. This is useful in cases where you are using this action in multiple workflows using the same trx files as inputs e.g. matrix builds on multiple OSes.
    • It will make it easier to distinguish between outcomes from multiple workflows.

Add SHA input to trx-parser action

13 Aug 16:03
2ba59ca
Compare
Choose a tag to compare
  • Resolves #191
  • Added a new SHA input to trx-parser action. This is useful in cases where trx-parser is used in a workflow triggered by events other than pull_request and push
  • Many thanks to @flcdrg for contributing on #192

Bugfix - Handle zero test results

14 Apr 15:29
39bdec5
Compare
Choose a tag to compare
  • This release contains fixes for #84 #111
  • Updated the README to add notes for #68 and #125

BREAKING CHANGE - only report failing tests

10 Feb 09:22
7257e83
Compare
Choose a tag to compare

BREAKING CHANGES

This release contains:

  • dependabot version updates and includes #96 #99 #100 #101 #102 and #104
  • The breaking change was introduced on #103 in response to #68. There is a hard limit on the GitHub checks api of 65k characters. If the report content exceed that limit then GitHub fails to create a check with an error like below
Only 65535 characters are allowed; 1607778 were supplied.

So in order to tackle the character limit, after communicating with a few users, I decided to only report the failing tests.
This change also introduces a new status badge on top of the report that look like the one below:

Passing Tests: Generic badge
Failing Tests: Generic badge

Security updates and bug fixes

08 Jan 23:01
7f6f63f
Compare
Choose a tag to compare

This release contains:

  • Several dependency version updates suggested by Dependabot
  • A fix for #77

Security patches by dependabot

21 Nov 22:11
56ab306
Compare
Choose a tag to compare

This release contains security patches by dependabot

Create status check on push event

06 Nov 17:16
Compare
Choose a tag to compare

Fixed #31
Allow generating status check on the push events.
The previous versions only allowed status checks on pull requests.