Repository navigation
feat(compose): Hasura v2.51 as the v1.5 default with upgrade smoke (P7-LIVE-23) - #707
Merged
Merged
Conversation
…7-LIVE-23) The image lock gains hasura (graphql-engine v2.51.0) and hasura-v14 (v2.44.0). v1.4 renders hasura-v14, v1.5 hasura (HasuraEntry, one compat.V15 gate). An explicit HASURA_VERSION wins, a project lock pin is kept, and the update plan offers the entry of the mode and never moves a newer pin back. scripts/ci/hasura-upgrade-smoke.sh proves the upgrade on Linux with data, metadata, an event trigger, a remote schema and a subscription, plus both rollback paths.
…1 override (P7-LIVE-23)
…n both compat modes (P7-LIVE-23)
acamarata
force-pushed
the
p7/P7-LIVE-23
branch
from
October 12, 2026 08:30
71e1df9 to
4396517
Compare
…back comments, smoke row count (P7-LIVE-23) A digest-only pin of the hasura-v14 digest orders as v2.44.0, an unknown digest-only pin is left as is in both modes, the lock bootstrap test uses the entry of the mode, and the smoke counts the rows added since the backup from the database right before the restore.
…a build with no pin (P7-LIVE-23)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hasura(graphql-engine v2.51.0) andhasura-v14(v2.44.0), resolved with tools/imagelock (floating-tag drift in unrelated entries left out).hasura-v14, v1.5 rendershasura(compose.HasuraEntry, one compat.V15 gate). An explicit HASURA_VERSION wins (v2.51.0 now counts as an override; the init default v2.44.0 does not). A project lock pin is kept (TestHasuraLockPinKept).nself updateplan: the hasura row follows the mode, adds a one-way note for the v2.51 move and never moves a newer pin back.scripts/ci/hasura-upgrade-smoke.sh+ fixtures: start on v2.44.0 with migrated data and metadata (tracked tables, relationship, permission, event trigger, remote schema), verified backup, switch to v2.51.0, assert rows, metadata export equality, mutation, subscription, remote schema, event trigger; rollback by restore; pin-back without restore observed.Verification
Evidence is kept in the hq QA folder (P7-LIVE-23-verify.out, smoke-v15.out, smoke-v14.out; both smokes ran on mm4, Colima linux/arm64).
Ticket: P7-LIVE-23 (draft; not for merge until the lead reviews)