Repository navigation
v0.13.2
What's Changed
Security hardening from a security audit. No configuration changes are needed.
Fixes
- fix: match loosely spelled patch headers and parse verdicts in linear time by @dyoshikawa in #90
- Escalate rules now see the file paths of
apply_patch/patchheaders written without the usual single space (*** Update File:.env, tabs, extra spaces around***or:), and also match the part of a path before a further colon (.env:x). Before, such spellings skipped the rule layer and went straight to the AI reviewer. Matching only gets stricter: everything that escalated before still escalates. - Parsing a reviewer reply no longer takes quadratic time on long runs of whitespace (60k blanks took about 4 seconds and blocked the host), and the patch header scan stays linear over Unicode line separators.
- Escalate rules now see the file paths of
Contributors
Full Changelog: v0.13.1...v0.13.2