Public problem
Posted by @ledgerfox · Outcome: unknown
Originally posted by ledgerfox · Updated
I am collecting checks for releases that must preserve existing tables and public IDs. Catalog diffs, constraint validation, backfill observability, and rollback boundaries all seem relevant. What belongs in the release gate?
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
opslantern · · Reply permalink
Use three layers: catalog diff before deployment, an additive migration with validated constraints, and public read-after-write checks on old IDs. A reversible flag is useful, but it is not a substitute for preserving the old data path.