Skip to content
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

chore: bump to PostgREST v12.2.8 #1515

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

Conversation

laurenceisla
Copy link

Bumps PostgREST from v12.2.3 to v12.2.8 (patch release).

Adds some bug fixes like JWT cache not removing expired entries and showing 503 HTTP errors in the logs (useful for support using Logflare).

@laurenceisla laurenceisla requested review from a team as code owners April 2, 2025 12:54
Copy link
Collaborator

@samrose samrose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@laurenceisla let me know if you help testing this in local infra/integration context. Other than that step, approving thanks!

@samrose
Copy link
Collaborator

samrose commented Apr 2, 2025

@laurenceisla sorry also please advance the versions in ansible/vars.yml one more than where they are at in develop branch please

ansible/vars.yml Outdated
Comment on lines 12 to 14
postgresorioledb-17: "17.0.1.57-orioledb"
postgres17: "17.4.1.007"
postgres15: "15.8.1.064"
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry also please advance the versions in ansible/vars.yml one more than where they are at in develop branch please

These are the versions to advance, right?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@laurenceisla yeah you got it. If you need to test in local infra prior to merge to develop you can also add a suffix to those as well, and then create a pre release ami to test in local infra too.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thanks!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@samrose I'm having some issues pinpointing why the tests are not running. The AMI builds pass correctly, but it times out waiting for the postgrest service when running the tests.

https://github.com/supabase/postgres/actions/runs/14246128670/job/39927529001#step:13:275

I tried testing on a local environment and I managed to run the infra stack, but I'm not sure how to generate a Postgres pre-release to add to the middleware and test this issue locally:

you can also add a suffix to those as well, and then create a pre release ami to test in local infra too.

Are there any docs I can follow?

@laurenceisla laurenceisla force-pushed the pgrst-12.2.8 branch 5 times, most recently from d0f5912 to 957fe05 Compare April 3, 2025 14:55
@laurenceisla laurenceisla marked this pull request as draft April 3, 2025 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants