Repository navigation
ci(release)!: v22 - #341
Draft
dargmuesli wants to merge 2 commits into
Draft
dargmuesli wants to merge 2 commits into
dargmuesli wants to merge 2 commits into
Conversation
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.
What 22 means
Stack 22 moves the database to sqitch 13, which consolidates all previous migrations into a clean set of base migrations. Alongside it, the stack pins vibetype 17.1.0 and postgraphile 3.0.0, which are built against the sqitch 13 schema and its changed GraphQL API, so the three have to be upgraded together and none of them works with the previous generation of the others.
A database deployed by sqitch 12 cannot be upgraded in place: sqitch 13 no longer finds the recorded change history in its plan and
sqitch deployaborts withCannot find change ... in sqitch.plan. Deploying 22 the usual way would therefore fail on the database and leave vibetype 17 running against the old schema.To upgrade, follow
docs/sqitch-major-upgrade.mdinstead of a plain deploy. It renames the old schemas, lets sqitch 13 deploy fresh ones next to them, and copies the data across withdocs/sqitch-major-upgrade.sql, keeping only the columns both versions share and reporting the rest. Rehearse it first on a copy of production data withdocs/sqitch-major-upgrade-rehearse.sh, which fails when a row goes missing, and plan for downtime from stopping the services until the new stack is up.