Repository navigation
v0.3.0
Features
- Add
requires:to frontmatter and project config (#54). Each named command must
resolve on the PATH its sessions will use before any session runs; otherwise the run
stops and names the command, the file, and every directory searched. Each resolution
is reported, for example
resolved my-cli -> /repo/target/debug/my-cli (12 files, 129 sessions), so a suite
shows which build it exercised instead of silently falling through to an installed
copy.
Fixes
-
Drop a
path:entry that expands to an empty string, such as a bare$TOOL_DIR
whenTOOL_DIRis unset (#55). The entry used to resolve to the test file's
directory, so a command lookup could find a stray executable among the test's own
files instead of failing with "command not found". A run whose inheritedPATHis
unset or empty also no longer gets an emptyPATHelement, which POSIX reads as the
working directory.This can turn a false pass into a real failure: a test that only passed because
its command was found in the test directory through an unresolvedpath:entry now
reports that the command was not found.
Dependencies
-
Replace
fast-globwithtinyglobbyfor test discovery (#56). This removes
micromatchandbracesfrom the dependency tree, clearing GHSA-vfj7-8cjw-p6xm
(CVE-2026-93687, stack-exhaustion denial of service inbraces, no patched release)
from the audit of every project that depends on tryscript.Patterns under the working directory select the same files as before. Two edge cases
change:- A pattern that climbs above the working directory, such as
../**/*.tryscript.md,
now skipsnode_modulesanddistdirectories and honors!patternexclusions,
as every other pattern already did. - An absolute pattern no longer matches nothing because a directory above the
working directory is nameddistornode_modules.
- A pattern that climbs above the working directory, such as