-
-
Notifications
You must be signed in to change notification settings - Fork 174
chore: bump to PostgREST v12.2.8 #1515
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
base: develop
Are you sure you want to change the base?
Conversation
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.
@laurenceisla let me know if you help testing this in local infra/integration context. Other than that step, approving thanks!
@laurenceisla sorry also please advance the versions in ansible/vars.yml one more than where they are at in develop branch please |
4ef44dd
to
dd3f4ef
Compare
d0f5912
to
957fe05
Compare
957fe05
to
7b14d8a
Compare
After testing in the instance, $ opt/postgrest --version
/opt/postgrest: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /opt/postgrest)
/opt/postgrest: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /opt/postgrest)
/opt/postgrest: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /opt/postgrest) |
@laurenceisla what is the version of glibc you need? 2.34? |
...the version in the current release of ami is 2.31 fwiw |
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).