You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Align GitHub Action with CTRF 0.5.0 and report identity - #332
Update the Action to CTRF 0.5.0 and the latest AI, JUnit, Teams and Handlebars helper releases. Refresh dependencies and tooling, retaining the existing Slack version and Node 24 runtime requirement. Prepare version 1.3.1.
Keep historical test matching unchanged: comparisons continue to use test names, including metrics and added/removed tests. Adding test IDs does not reset historical metrics. Defer ID-based matching until a migration strategy preserves existing history.
Preserve test, execution and attempt IDs while giving changed, merged and grouped report artifacts fresh IDs. Preserve shared explicit run IDs and remove ambiguous shard labels from merged reports. Generated conforming reports use specification 0.2.0; legacy inputs retain compatibility handling.
Rebuild the committed Action bundle with all six CTRF schemas. Adapt updated artifact SDK IDs safely and fix bundled CommonJS global collisions. Keep the README focused on existing usage.
Validation:
Node 24: type checks, Biome checks, 127 tests and coverage pass. Badge generation completed with network access after sandbox DNS failed; packaging and built Action syntax checks pass.
Five name-matching regression cases cover name-only history, newly added test IDs, legacy ID migration, changing legacy IDs and different logical IDs with the same name.
Historical insights source matches the PR base byte-for-byte. Real old/new JUnit conversion retains history without false additions/removals.
Actual built Action processes CTRF and JUnit files, preserving identities and grouped results.
Dependency refresh previously verified with clean install/full checks, zero full and production audit findings, and registry signature verification; this follow-up changes no dependencies.
Packaged schemas match installed CTRF byte-for-byte; current schema matches the authoritative specification.
Ma11hewThomas
changed the title
Upgrade CTRF to 0.4.0 and fix npm audit findings
Upgrade CTRF to 0.4.0 and correct generated report versions
Oct 4, 2026
Ma11hewThomas
changed the title
Upgrade CTRF to 0.4.0 and correct generated report versions
Align GitHub Action with CTRF 0.5.0 and report identity
Oct 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ma11hewThomas
changed the title
Update the Action to CTRF 0.5.0 and the latest AI, JUnit, Teams and Handlebars helper releases. Refresh dependencies and tooling, retaining the existing Slack version and Node 24 runtime requirement. Prepare version 1.3.1.
Keep historical test matching unchanged: comparisons continue to use test names, including metrics and added/removed tests. Adding test IDs does not reset historical metrics. Defer ID-based matching until a migration strategy preserves existing history.
Preserve test, execution and attempt IDs while giving changed, merged and grouped report artifacts fresh IDs. Preserve shared explicit run IDs and remove ambiguous shard labels from merged reports. Generated conforming reports use specification 0.2.0; legacy inputs retain compatibility handling.
Rebuild the committed Action bundle with all six CTRF schemas. Adapt updated artifact SDK IDs safely and fix bundled CommonJS global collisions. Keep the README focused on existing usage.
Validation:
git diff --checkpasses.