Repository navigation
Support Test attemptId from CTRF 0.2.0 - #87
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.
Supports optional Test-level
attemptIdfrom CTRF specification v0.2.0, with the same non-empty string definition as retry history. Adds the public library type and TestBuilder setter, copies the accepted schema verbatim and retains historical schema validation. Existing README examples and builder/validation suites cover the field. Deprecated CLI types remain unchanged; users should migrate to the standalone ctrf-cli package.Prepares stable
ctrf@0.5.0for staged publication tolatest; the specification version is 0.2.0. Release workflow is unchanged; staged npm approval and final GitHub release publication remain separate maintainer steps. Also retains the scoped development lockfile fix for source-map-js.Validation: npm ci and npm run all pass (243 tests); source/built schema byte comparisons, attw, declaration smoke, fresh packed CJS/ESM and deprecated CLI checks pass. Production audit is clear; one existing low development-only esbuild finding remains. Registry signatures and attestations verify. TypeDoc retains existing relative-link warnings.