runward 0.46.0
Five decisions an adopter’s reports led to are shipped, and a JUnit report that records failures is no longer sealed.
What changes
check --freezerefuses to seal a cited JUnit report that records failures or errors, even when the cited cases are green. It is the one verdict that changes.- The strict check says how many rows rest on a committed JUnit report, and that its freshness is not verified by this command; a CI recipe, for GitHub Actions and GitLab CI, checks it.
- The EU AI Act pack names what falls to the operator: the system’s qualification and Articles 4, 5, 14 and 50. runward supplies nothing for them, it names them so their absence shows;
--regime-version eu-ai-act@2026-1744keeps the previous output byte for byte. - Two crosswalks, GDPR and NIS2, say which runward artefacts an entity may cite as supporting evidence for which article, and name the articles runward does not touch.
- For a system of several repositories: one record per repository, and a system document that cites each member by its digest, never adding their verdicts together.
Source
This note restates the section “0.46.0” of runward’s CHANGELOG, at the tag v0.46.0, and nothing else. The detail, and what it leaves out, is in the release notes on GitHub.