runward 0.36.0
The evidence your delivery chain already produces now counts, and the verdict leaves in the formats your tools already read.
What changes
- The verdict leaves as SARIF (
check --sarif), annotated on the row concerned in the pull request, and as a SLSA verification summary (check --vsa), claiming no SLSA level. - A rule can rest on a report your CI already commits: a SARIF scan, lcov or Cobertura coverage, an ESLint report, a CycloneDX SBOM. A report that itself records a problem is not evidence.
spec-checkreads a whole specification folder: every criterion it references must be declared in it.- Two false greens found in runward’s own code are fixed: a red test hidden behind a green test of the same name, and a criterion read as linked without its pointer being checked.
- The same working tree gives the same verdict on three operating systems, Windows included, now run in CI.
Source
This note restates the section “0.36.0” of runward’s CHANGELOG, at the tag v0.36.0, and nothing else. The detail, and what it leaves out, is in the release notes on GitHub.