You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c20df92
Browse filesBrowse the repository at this point in the historyBrowse files
test(stack-prisma): run the shipped edges' own SQL in the live suite
The live migration suite only ever applied the installed
@cipherstash/eql's SQL, so no carrier op's or upgrade edge's postcheck
ever ran against a database. Those postchecks compare against literals
interpolated at emit time (`eql_v3.version() = '3.0.6'`), so one that
never matches what its own edge installs fails every customer apply
while every offline test stays green.
Two cases now apply the descriptor's baked SQL the runner's way:
execute, then postchecks, one transaction per plan.
- db init: the genesis edge alone, on an empty eql_v3, satisfies every
one of its postchecks.
- migrate: a 1.1.x database walks the 3.0.5 then the 3.0.6 edge. It
starts from the 3.0.4 edge's bytes, which are the 1.1.x baseline's
(both pin 63104a81). Each edge is asserted NOT pre-satisfied first,
because the runner skips an op whose postchecks already hold, so the
double install the 3.0.6 changeset warns about is shown to be real.
The end state then satisfies the genesis edge's postchecks.
Ops are typed by extending the framework's MigrationPlanOperation, as
stale-vendored-space.test.ts does, so the descriptor's ops narrow to
them without a cast across unrelated types.
The byte-identity case stays, and is red by construction between this
branch merging and #938 doing so. The baseline then bakes 3.0.6 while
the installed package is still 3.0.5. The comment there and
DEVELOPING.md say so.
Verified against ghcr.io/cipherstash/postgres-eql:17-2.3.1. On this
branch 6 of 7 pass; byte-identity fails, and its diff is exactly the
two stamp lines. With #938's EQL files applied all 7 pass. Two
mutants fail as they should. Dropping the 3.0.6 edge from the walk
gives "expected '3.0.5' to be '3.0.6'". A 3.0.5 bundle checked against
the genesis postchecks fails the 3.0.4 carrier's version check.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PaY5xYydZUWhv8Nex9Sw8a
0 commit comments