feat: bump to PostgREST v14.18 - #2446
Merged
Merged
Conversation
Contributor
Author
|
Smoke tests pending, will update once they're done. |
steve-chavez
approved these changes
Sep 11, 2026
laurenceisla
force-pushed
the
laurence/pgrst-14.18
branch
2 times, most recently
from
September 12, 2026 00:57
71a7f66 to
ae81bb6
Compare
Contributor
Author
|
All smoke tests are passing (Sep. 11): https://github.com/supabase/supadev/actions?query=actor%3Alaurenceisla The |
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
2 participants
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.
What kind of change does this PR introduce?
Bumps PostgREST from v14.17 to v14.18
What is the current behavior?
v14.17 did not fix the "JWT issued at future" issue.
What is the new behavior?
We tested the fix included in v14.18 on affected projects and the problem didn't reappear.