Skip to content

Invaris v0.4.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 07:43
· 27 commits to main since this release
c7e1866

Invaris v0.4.0

Invaris 0.4.0 helps a developer run a first useful experiment and read the result: invaris doctor finds setup problems before a run, invaris explain says what a saved report does and does not show, and a harness can now run in a Node project with node_modules installed.

  • invaris init creates .invaris/invaris.json; commands prefer that file and fall back to the root-level configuration when it is absent. Existing root-level files remain supported, and init refuses to create a competing configuration. Campaign configuration can also live in .invaris; see authoring and campaigns.
  • An invaris-cli npm package is prepared for publication, containing the CLI and command provider for Linux and macOS on amd64 and arm64. npm installation requires Node.js 22.14 or later; see the installation guide for current availability.
  • invaris doctor [HARNESS] inspects a harness without running any of its commands. It checks that the harness loads and which actions it supports, that the directory can be copied into a workspace (the check that names an installed node_modules or a symbolic link), that each program is found in the PATH its command would use, allowlisted variables that are unset, that targets exist, that literal edit markers occur exactly once, that built-in operators apply and pinned preimages still match, and that writable paths exist. Provider discovery is reported as skipped because it would run the adapter. Exit 0 means nothing failed and 1 means a setup check failed.
  • invaris explain REPORT reads a v1alpha2 to v1alpha5 report offline, validates it, and labels each result detected, missed, inconclusive, excluded, passed, failed or not-run, with the meaning and next step of its recorded reason. It lists limits such as weak marker evidence, a portable profile that withholds details, a dirty working tree and an incomplete decision. A report that fails validation, such as one whose decision was edited, is refused.
  • Mutation (v1alpha3) and challenge (v1alpha4) harnesses accept an optional workspace block. dependencies links top-level directories such as node_modules beside the disposable copy instead of copying them, so Node and Vite resolve packages while the copy holds no link into the source. exclude leaves build output and tool caches such as .next out of the copy and its integrity snapshots. maxEntries raises the 2000-entry bound up to 200000. A campaign combines the blocks of the harnesses it references. See workspace options.
  • A workspace_changed result now names what changed, up to 20 paths marked + (added), - (removed) or ~ (changed), such as +node_modules/.vite/deps. The entry-limit and symbolic-link refusals say which workspace field resolves them.
  • Both commands print text by default and JSON with --format json; the JSON is described by new schemas. Neither command writes a report or runs project code.
  • A self-check experiment shows the whole workflow on this repository: a healthy baseline, a detected fault, a missed-detection control, a killed and a surviving mutant, and a campaign, with a friction log and what doctor and explain changed.

Existing root-level harnesses, report versions and verification exit codes remain supported; the default location created by init and configuration discovery have changed as described above. A harness that uses the workspace block needs 0.4.0; earlier binaries refuse it as an unknown field rather than ignore it. Reports are not authenticated: matching hashes show that bytes are consistent, not who ran a check or how.

Known limitations:

  • doctor cannot tell whether a command prints the result object its role requires, or whether go run ./tool compiles, because that would mean running it. It inspects one harness at a time; run it for each file a campaign names.
  • Without a workspace block, a checkout with node_modules installed still cannot be copied: the default copier refuses symbolic links and more than 2000 entries, and doctor names the offending path. dependencies accepts only top-level directories; a nested node_modules can be excluded but not linked.
  • Excluded paths and dependencies are outside the integrity check. A command can change them, or write through a dependency link into the source, without the run noticing. The harness digest in each report pins the options, but a campaign report's sourceIdentity.excluded still lists only .git and .invaris.
  • The self-check experiment below was run before the workspace block existed and has not been repeated with it.
  • Two smaller friction items from the self-check are unchanged: --report refuses to overwrite an existing file, and a challenge with a missed control exits 1; explain shows the decision but does not explain the exit code.
  • The self-check has not yet been repeated by a second operator, which the roadmap asks for before claiming that the workflow generalises.

Linux and macOS archives for amd64 and arm64 include both invaris and invaris-command-provider, a README and the Apache-2.0 license. Verify downloads with SHA256SUMS. No Go installation is needed to run the binaries; source builds require Go 1.27.4 or later. Windows is supported through WSL using the Linux archives.

Commands run with your user permissions and can access the network and external files. Disposable copies are not security sandboxes.

See the changelog, diagnostics, installation guide, evidence reference and threat model.