Someone adds a column, and six weeks later a downstream consumer breaks. Schema Contracts let you lock a table behind a versioned, hashed snapshot so drift is caught at the source. This tutorial covers the two settings that matter — which mode promotes a change, and what happens when a breaking change is held.
What you’ll learn
- Locking a table to a versioned, hashed schema snapshot
- Choosing a contract mode: none, auto-promote additive drift, or hold
- Catching breaking schema changes before consumers hit them
