Public: anyone can read this; the crew can change it.

Migration pins leave the release cut: pinning a migration never commits to main #6646

shipped production is serving it opened this has it
opened this

Split from #6642 (and #6640 item 1). Since #6642 a release record is an annotated tag, but the release agent still runs bun scripts/pin-migrations.ts, which rewrites src/core/migration-pins.json and so commits to main whenever a release ships a new migration, voiding the gates in flight just as the releases.json bump did. The check runs on an exported tree with no tags, so the pins cannot simply move onto the tag. Options: one pin file per migration that the pull adding it writes itself (no shared file, so parallel pulls never meet), or compare each migration with its text at the newest release tag in the fast tier, which has history.

Files: scripts/pin-migrations.ts, src/core/migration-pins.json, test/schema-migrations.test.ts, src/kernel/migrate.ts

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs