Repository navigation
Release v7.148.0
Summary
Behavior changes on trust-boundary and wire or protocol surfaces now have to cite and conform to the published contract that governs them, and reviewers block changes that do not.
Added
- A
published-contracts.mdrule: before changing behavior at a trust boundary or wire/protocol surface, find the published contract and its conformance vectors and cite them in the issue and pull request (or state that none exists); when a change conflicts with a vector the contract wins, so change the contract through its owner first; repositories that implement a contract run its pinned vectors as executable specs in CI (#1087)
Changed
- The rule index in
general.md, the review-report rules and the code and security reviewer agents now treat an uncited behavior change on such a surface, or one that conflicts with a vector, as a blocking finding (#1087)