This release includes 1 security fix for security teams reviewing exposed deployments.
Topics
+9 more
Summary
AI summaryFixed misclassification of pytest logs as failures, prevented crashes from non‑array hits.json, and neutralized markdown injection in reports.
Full changelog
## v0.10.2 — closing the live fuzz-review findings
A 46-agent fuzz/review pass ran against a 0.9.0 checkout, so most of its HIGH findings (failCount mixing, positional eviction, mtime locks, recordHit-before-deny, settings clobber, unpinned CI) were already fixed in 0.10.0/0.10.1 — re-confirmed fixed, not re-patched. Four findings genuinely reproduced on HEAD and are closed here, each with an adversarial test:
- Cross-toolchain false FAIL. A passing pytest run whose log contained a jest-style
FAILbanner — orRetrying 1 failed attemptprose — was misclassified as a failure (and would have wrongly blocked the correct fix on a later session). Classification is now scoped to the runner's own patterns via the command. loadHitscrash. A valid-JSON-but-not-arrayhits.json(e.g.{}) crashedrl stats/rl report; now coerced to[].- Markdown report injection.
rl reportmarkdown embedded ledger text verbatim; headings/code-fences from a crafted preview are now neutralized (the HTML renderer already escaped).
100 tests - benchmark green - zero dependencies. The honest pattern holds: ship fast, review adversarially, and let the changelog keep its own ledger.
Security Fixes
- Markdown report injection neutralized in `rl report`
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Regressionledger
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]