Repository navigation
Prepare jtest 0.2.0 for Jo 0.14 - #1
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
1 participant
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.
Prepare jtest 0.2.0 for Jo 0.14.0, which uses an incompatible SAST 2.0 format. Rebuild the shared core and both runtime packages together as 0.2.0; their artifacts record Jo 0.14 and the runner dependency on core 0.2.
Runner.runWithArgsnow returnsUnitand exits nonzero when selected tests fail. The README shows the direct call, andRunner.runremains available when callers need to handle the Boolean result. Python and Ruby failure fixtures verify the process status and diagnostic.Validation passed locally with Jo 0.14.0: both conformance apps, report parity, expected nonzero failure checks on both backends, all three package builds, and all six SHA-512 checks.