When a code change reaches
further than its diff
Five situations where release risk can spread beyond the files that changed.
- cross-components
- agent-written code
- Dependencies
- DevOps
- Security & compliance
Correct code can still change working behaviour
Review and tests can pass while business behaviour changes.
Is this code sound?
Do known cases still pass?
What the diff cannot show
Blast radius
See the business flows at risk across the project and configured component relationships.
Behavioural difference
Compare the release candidate with production to identify which business behaviours changed.
Expected or regression
An unexpected change is a regression.
Traceability
Keep each result linked to its PR, commit, author, timestamp and run.
Where the risk appears
Cross-component changes
A provider change can move a dependent consumer flow.
An agent writes the code and tests
Shared assumptions can make both agree and both be wrong.
Dependency changes
A package or shared module update can move behaviour in consumers that rely on it.
DevOps changes
Config, infrastructure, or environment changes can alter runtime behaviour without large code diffs.
Security and compliance review
Access, authentication, and audit-sensitive changes need evidence of what moved before release.
