Merged
Conversation
Contributor
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. |
Contributor
Author
🚀 Production Deployment: Website✅ Successfully deployed to production! 🔗 Production URL: https://pgflow.dev 📝 Details:
Deployed at: 2025-10-30T18:46:18+01:00 |
Contributor
Author
🚀 Production Deployment: Playground✅ Successfully deployed to production! 🔗 Production URL: https://playground.pgflow.dev 📝 Details:
Deployed at: 2025-10-30T18:46:18+01:00 |
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
pgflow@0.7.1
Patch Changes
@pgflow/client@0.7.1
Patch Changes
@pgflow/core@0.7.1
Patch Changes
a71b371: Fix installation failures on new Supabase projects by removing pgmq version pin.
Supabase upgraded to pgmq 1.5.1 in Postgres 17.6.1.016+ (feat: support multiple versions of the pgmq extension supabase/postgres#1668), but pgflow was pinned to 1.4.4, causing "extension has no installation script" errors on fresh instances.
Only affects new projects - existing installations are unaffected and require no action.
Thanks to @kallebysantos for reporting this issue!
@pgflow/edge-worker@0.7.1
Patch Changes
@pgflow/example-flows@0.7.1
Patch Changes
@pgflow/dsl@0.7.1
@pgflow/website@0.7.1