fix: Re-enable extension upgrade test, this time for PG16 onwards #778
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
philippemnoel
requested review from
rebasedming,
neilyio and
sardination
as code owners
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.
Ticket(s) Closed
What
I had disabled it since it was broken due to the switch to PG16. The reason is: Our test pulls a previous version of the extension pre-compiled from a past GitHub Release, installs it, then upgrades to the current branch. Since we had just pushed our first PG16 extension, and you can't upgrade from PG15 to PG16 without directly installing a brand new version of the extension compiled for PG16, I had nothing to test installing it against. Now that we've had a few releases, we can do it.
Why
^
How
^
Tests
^