Fix cellular manifest parser alias collision
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (postgres) (push) Failing after 32m36s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-12 03:00:34 -04:00
parent 65e007cc86
commit a11f0c8e0f
2 changed files with 9 additions and 3 deletions
+6
View File
@@ -7079,3 +7079,9 @@ increased the 360-byte manifest to 364 bytes. Migration 32 now intercepts v3
manifests, writes the four-byte little-endian value directly, and delegates to
the preserved v27 parser. The PostgreSQL migration integration test covers the
v1-to-v2-to-v3 path. CI validation and Harbor image publication are pending.
CI run #326 compiled the PostgreSQL targets but failed while applying migration
32: it tried to rename the current parser to `parse_checkpoint_manifest_v27`, a
name already created by migration 28. The pending migration now uses the unique
`parse_checkpoint_manifest_v31` alias. The PostgreSQL gate and Harbor image
publication are pending another CI run.