ci: bump postgres version to 14.20 #1719
Merged
Conversation
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
In line with getodk/central#1546 Closes getodk/central#1571
sadiqkhoja
approved these changes
Dec 16, 2025
added 2 commits
December 16, 2025 16:40
…0, '' }} rebuild
…words: 30, '' }}" This reverts commit 1d6bc03.
Contributor
Author
|
CircleCI haven't published a postgres image for 14.20 yet. I've filed at CircleCI-Public/cimg-postgres#148. I will also change |
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.
In line with getodk/central#1546
Closes getodk/central#1571
What has been done to verify that this works as intended?
CI: https://github.com/getodk/central-backend/actions/runs/20260281193/job/58170600348?pr=1719:
Why is this the best possible solution? Were any other approaches considered?
No other approaches considered.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
No effect.
Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.
Maybe there's some docs/script for dependency updates this could be included in?
Before submitting this PR, please make sure you have:
make testand confirmed all checks still pass OR confirm CircleCI build passes