Repository navigation
feat(sqitch)!: upgrade to v13 - #333
Merged
Merged
Conversation
# Conflicts: # src/production/vibetype/compose.yaml
# Conflicts: # src/production/vibetype/compose.yaml
dargmuesli
enabled auto-merge (squash)
November 11, 2026 13:35
|
🎉 This PR is included in version 22.0.0-beta.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This was referenced Nov 11, 2026
Draft
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.
sqitch 13 consolidates its migrations into a clean set of base migrations, so a database deployed by sqitch 12 cannot be upgraded with a plain
sqitch deploy, which aborts withCannot find change ... in sqitch.plan. This pins sqitch 13.0.0 in production and documents the dump, upgrade and restore cycle indocs/sqitch-major-upgrade.md: the old schemas are renamed, sqitch 13 deploys fresh ones next to them, anddocs/sqitch-major-upgrade.sqlcopies the data across, taking only the columns both versions share and reporting the rest, then checks foreign keys and rebuilds the event search vectors.docs/sqitch-major-upgrade-rehearse.shruns the whole procedure against a postgres-backup dump on a throwaway database and fails when a row goes missing. It also pins vibetype 17.1.0 and postgraphile 3.0.0, which match the sqitch 13 schema, and keeps theNUXT_PUBLIC_SENTRY_ENABLEDflag from #334 that vibetype 17 needs to report to Sentry.Closes #335, closes #337