Fix cellular v3 manifest normalization
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (postgres) (push) Failing after 33m10s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-12 02:24:21 -04:00
parent 7842703230
commit 65e007cc86
5 changed files with 65 additions and 8 deletions
+8
View File
@@ -7071,3 +7071,11 @@ unique across the database, and that fixture uses sixteen `0x50` bytes. The
cellular migration genesis ID now has a distinct first byte while preserving
the remaining test pattern. CI must rerun the PostgreSQL gate and downstream
Harbor publish before a server image is available.
CI run #325 reached the v2-to-v3 cellular profile migration and rejected the
normalized manifest as malformed. The v3 parser was replacing a four-byte
history-profile field with the eight-byte result of `manifest_u64le(3)`, which
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.