chore: upgrade PostgreSQL 17 and Supabase CLI 2.54.11 #300
Conversation
🦋 Changeset detectedLatest commit: c35fab0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
View your CI Pipeline Execution ↗ for commit c35fab0
☁️ Nx Cloud last updated this comment at |
jumski
force-pushed
the
chore-update-supabase-versions
branch
4 times, most recently
from
8f99711 to
b05ba56
Compare
jumski
force-pushed
the
chore-update-supabase-versions
branch
6 times, most recently
from
eba7284 to
f8447bd
Compare
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
|
|
||
| **File**: `pkgs/core/schemas/0080_function_read_with_poll.sql` (entire file) |
There was a problem hiding this comment.
The PR description and PLAN.md mention deleting schemas/0080_function_read_with_poll.sql as part of Task 2, but this file deletion isn't included in the actual PR diff. This backport function should be removed since PGMQ 1.5.1 includes the fixed version natively.
Consider adding this deletion to complete the migration from the custom backport to the native implementation, which aligns with the comment in the file that states it "will be removed once Supabase upgrades to 1.5.0 or higher."
Spotted by Graphite Agent
Is this helpful? React 👍 or 👎 to let us know.
…kerfiles, and scripts - Changed major_version from 15 to 17 in multiple config files for various environments - Updated Dockerfile to use postgres:17 and related build scripts for new image - Modified Atlas setup to rely on custom postgres:17-pgmq image - Adjusted database type definitions for compatibility with PostgreSQL 17 - Updated compose files to reference the new PostgreSQL 17 image - Added note in documentation about PostgreSQL 17 support and migration guidance
jumski
force-pushed
the
chore-update-supabase-versions
branch
from
f8447bd to
c35fab0
Compare
Summary
This PR upgrades the pgflow project to PostgreSQL 17 and Supabase CLI 2.54.11, removing strict version pins for Docker images and the PGMQ extension to use the latest compatible versions.
Changes
PostgreSQL Version Upgrade
pkgs/core/atlas/Dockerfile)pkgs/edge-worker/tests/db/compose.yaml)config.tomlfiles)pkgs/core/atlas/atlas.hcl)PGMQ Version Management
Configuration Updates
Updated PostgreSQL version references in:
examples/playground/supabase/config.tomlpkgs/client/supabase/config.tomlpkgs/core/supabase/config.tomlpkgs/edge-worker/supabase/config.tomlpkgs/core/atlas/atlas.hclDatabase Types
pkgs/core/src/database-types.ts) to reflect PostgreSQL 17 schemapnpm-lock.yamlCleanup
pkgs/core/supabase/.temp/pgmeta-versionpkgs/core/supabase/.temp/postgres-versionDocumentation
pkgs/website/src/content/docs/deploy/update-pgflow.mdxfor upgrade proceduresTesting
All existing tests pass with PostgreSQL 17. No functional changes to pgflow behavior.
Impact
Related