Skip to content

Commit 4f8fc2d

Browse files
docs(platform-migrations): drop the watermark and cover untagged builds
Two review questions on the ordering design, answered together. Builds no tag has sealed yet (main, backports, PR e2e) carry slugs the tag walk cannot place, and the fatal "slug in no batch" rule would fail them. The generator now puts those slugs in a trailing order.d/99999-untagged and refuses to emit it for a checkout that is itself a tag, so a broken tag walk cannot ship. Batch numbers are per line, so a stored complete-through compared with another line's numbering could cover a batch the cluster never ran. The watermark had no reader beyond compaction, and compaction removed keys of slugs that still ship. Both go: keys are never deleted, the ledger records the manifest file name in batch as information only, and the retention floor check becomes a per-slug test that every retired slug has a ledger key. Fresh-install seeding covers retired entries so that check passes on a new cluster. Also aligns the state names on skipped-fresh-install and failed. Assisted-By: LLM Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent f962d16 commit 4f8fc2d

1 file changed

Lines changed: 30 additions & 27 deletions

File tree

  • design-proposals/platform-migrations

0 commit comments

Comments
 (0)