Repository navigation
SPOC-210, SPOC-235: Provide upgrade path to 1.2.1, display version - #22
Merged
Merged
Conversation
mason-sharp
changed the title
Prepare for v1.2.1
mason-sharp
force-pushed
the
fix/SPOC-210/lolor-pg18
branch
from
September 24, 2025 04:32
981f0c3 to
9e67ece
Compare
rasifr
approved these changes
Sep 24, 2025
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.
The original intent was to support Postgres 18. This is already supported on the main branch, so prepare for a new release, v1.2.1.
In the past, the SQL files were not maintained for v1.1 and v1.2, address for v1.2.1.
Also done- SPOC-235: make sure the version is displayed properly. I tested a new install and upgrade scenarios and verified that
\dxinpsqldisplays the version properly.