Migration test #1183
Draft
Migration test #1183
Conversation
This file contains 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
Closed
|
Once this settles out, could you please also update the migration testing doc https://github.com/supabase/postgres/blob/develop/nix/docs/migration-tests.md to reflect the new setup? |
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 kind of change does this PR introduce?
Migration testing that aligns with the workflow here but able to run locally against 2 versions of pg (currently just 15 -> 15)
This test is run with
nix run .#migration-test <git-tag-only> gitsha-or-gittag> pg_upgradeWe'll deprecate the "major version" as it is too vague to meaningful for the use cases for this tool.
This PR is WIP/Draft at this point, but prior to merging, we'll create specific tags for building and testing previous versions, and retain those in the git repo, and implement the support for gitsha or tag.