Bump PostgREST images to version 14.14 in Docker Compose stack - #21
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the Docker Compose stack to run a newer PostgREST container image version across all PostgREST-backed services, aligning the stack with the requested “bump to current” goal in the linked issue.
Changes:
- Bumped all
postgrest/postgrestservice images fromv14.11tov14.14.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
frankhereford
requested review from
Charlie-Henry,
chiaberry,
johnclary,
mateoclarke,
mddilley,
roseeichelmann and
tillyw
July 9, 2026 13:29
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.
Bump Postgrest Version to current
Issue
cityofaustin/atd-data-tech#28611
Testing
👀 on the code, and verify image exists, here.
Bonus points if you want to spin up the local instance, but I don't feel that this is required.
Deployment
On merge, I will deploy to production and restart the services. 🏁