A Release That Changes Defaults Changes Behavior Everywhere

Changed defaults reach every deployment that never overrode them, which makes a quiet defaults line in the notes the widest-reaching change in the release.

A new feature affects the teams that adopt it. A changed default affects every team that never made a choice, which is usually most of them.

Defaults review checklist

• Diff shipped defaults against your effective configuration.
• Flag defaults that alter permissions, timeouts, or retry behavior.
• Confirm which environments inherit versus override each change.

Use the changelog, security docs, and examples to trace every changed default to the deployments that inherit it.