Repository navigation
Release Testfold 0.4.6: truthful framework outcomes - #50
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Framework processes that exit unsuccessfully can currently appear green when their JSON reports contain passing assertions. This release makes process completion, parser completion and executed tests jointly determine success, while preserving partial assertion counts and useful failure diagnostics.
It retains the existing unmatched-file filtering contract and restores actionable Jest crash messages. Interrupted or timed-out partial inventories cannot produce invented unmatched-file failures.
Validation: the complete gate passed on Node.js 24.20.0 and npm 11.19.1, including 379 unit tests, 2 integration tests, workflow checks and an installed package consumer covering CLI, ESM and declarations. Independent implementation and final semantic reviews found no remaining issues.
The clean 0.4.6 candidate is accepted for publication through the trusted release workflow; its SHA-256 is
f65ae47fb6e2d9a6206774a85aa3d631dc56026aa734723b7dd59ffac867eaca.