-
-
Notifications
You must be signed in to change notification settings - Fork 228
feat: test pg_upgrade compatibility with older extension versions #1897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jfroche
wants to merge
10
commits into
develop
Choose a base branch
from
feat/test-pg-upgrade-older-version
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
c3d444d
feat: test pg_upgrade compatibility with older extension versions
jfroche 08457db
fix(pg_graphql): include unsupported versions as SQL-only for pg_upgr…
jfroche dbd3d51
fix(pg_jsonschema): include unsupported versions as SQL-only for pg_u…
jfroche 2f96685
fix(pg_stat_monitor): exclude v1.0 from pg_upgrade compatibility tests
yvan-sraka d29409d
fix(pg_stat_monitor): address review comments for latestVersion and l…
yvan-sraka e1e465b
fix(pg_jsonschema): broaden unsupported version detection beyond PG15…
yvan-sraka 39b92b2
fix(pg_jsonschema): remove debug find command from build output
yvan-sraka dc1c6d0
fix(pg_stat_monitor): use custom test instead of default for pg_upgra…
yvan-sraka 2fc828b
fix(pgmq): run after-create script before pg_regress test
yvan-sraka 66d2f75
fix(pg_graphql): use string comparison for pgVersion
yvan-sraka File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix typo in meta description.
"PostreSQL" should be "PostgreSQL".
Suggested fix
meta = with lib; { - description = "GraphQL support for PostreSQL"; + description = "GraphQL support for PostgreSQL"; homepage = "https://github.com/supabase/${pname}"; license = licenses.postgresql; inherit (postgresql.meta) platforms; };🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Funny typo, I suggest we fix it in another PR:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yvan-sraka, sounds good! That makes sense to address the typo across all files in a dedicated PR since it appears in multiple places.Would you like me to create a GitHub issue to track this typo fix? I can open one that lists all 5 occurrences across the codebase (README.md, nix/ext/wrappers/default.nix, and nix/ext/pg_graphql/default.nix) to make it easier to address them all at once.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you can open a new PR that fix it, that would be even better ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yvan-sraka, I'll create a PR to fix the typo across all files! Let me plan those changes.Task: Fix typo "PostreSQL" → "PostgreSQL" across codebase
💡 For code changes across multiple files, use
@coderabbitaiplan in an issue comment