Skip to content

tryscript v0.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Aug 02:51
· 16 commits to main since this release
v0.2.0
58172b5

tryscript v0.2.0 is a stability-focused minor release of correctness fixes,
strict validation enhancements, and additive public APIs. Valid v0.1.7 test files,
commands, options, export paths, and ordinary programmatic use remain supported.

What's Changed

  • Made --update and --expand lossless for duplicate blocks, bash fences,
    separate stdout/stderr assertions, CRLF files, and literal replacement text.
  • Corrected signal exit statuses, newline matching, wildcard capture alignment,
    deterministic discovery and LCOV output, and several formerly swallowed failures.
  • Added actionable errors for malformed executable Markdown and frontmatter, invalid
    configuration, unsafe fixture destinations, and failed hooks or requested artifacts.
  • Made TypeScript project configuration work from the packaged CLI on Node.js 20 and
    honor project-level test patterns when no files are passed.
  • Added the public validateConfig, TestParseError, and ConfigWarning exports while
    retaining every v0.1.7 named export and package export path.
  • Simplified tryscript docs and tryscript readme to deterministic raw Markdown for
    people, agents, and pipelines. The existing --raw and --color flags remain
    accepted as compatibility no-ops.
  • Hardened CI and publication with audited locked dependencies, minimum-Node package
    smoke tests, isolated npm OIDC authority, and npm provenance for the verified tarball.

Compatibility

No migration is required for valid v0.1.7 suites. This is a minor release because it
adds public APIs and strict enhancements; it does not intentionally remove supported
behavior.

Previously malformed or falsely successful cases can now fail with an actionable
diagnostic. When upgrading:

  • Split multiple $ prompts into separate executable fences, and close every
    executable fence.
  • Remove misspelled or stale configuration keys reported by validation warnings.
  • Investigate newly failing signal, hook, stderr, fixture, capture-log, or coverage
    cases; v0.1.7 could report false success for these failures.
  • If a script depended on ANSI-styled documentation output, render the returned raw
    Markdown in the caller.

See the full changelog
and all changes since v0.1.7.

Assets 2
Loading