fix: Pin embedded postgresql version to 16

[brendan-kellam]

In #753 I upgraded from node:20-alpine3.19 to node:24-alpine3.23. In alpine 3.23, I inadvertently introduced two version changes to our internally packaged redis & postgres dependencies:

• redis upgraded from 7.2.9 to 8.4.0
• postgresql upgraded from 16 to 18.

Redis can safely upgrade from 7->8 without issue. However, upgrading from postgres 16->18 (or between any postgres major versions for that matter) will result in errors that look like the following:

The data directory was initialized by PostgreSQL version x, which is not compatible with this version y.

This PR pins the postgresql version we ship in the embedded Docker container to 16. Additionally, it pins the postgres and redis versions used in the docker-compose.yml to 16 & 8 respectively.

Note: By pining versions in the docker-compose, there may be instances where folks run into errors during migration when 1) they updated their docker-compose.yml to this new revision with pinned versions, and 2) their previous latest for postgres was > 16. In this case, the POSTGRES_VERSION env-var can be set to whatever version they were on before.

Fixes #768

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}