Skip to content

chore(deps): update postgres docker tag to v18 #16

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.

Sign up for GitHub

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

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update postgres docker tag to v18 #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion compose.dev.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ services:

postgres:
Copy link
Copy Markdown

@sentry sentry Bot Feb 1, 2026

Choose a reason for hiding this comment

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

Bug: Upgrading the PostgreSQL image from version 15 to 18 without a data migration strategy will cause the database service to fail on startup if an existing data volume is present.
Severity: CRITICAL

Suggested Fix

Include a data migration strategy for existing deployments. This could involve adding a manual upgrade step to the deployment process using pg_dump and pg_restore, or creating an initialization script that handles the data migration automatically. Alternatively, if this is for new deployments only, document that the volume must be cleared.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: docker-compose.yml#L22

Potential issue: The `docker-compose.yml` file updates the PostgreSQL image from version
15 to 18. PostgreSQL data directories are not compatible across major versions. When the
new container starts, it will attempt to use the existing data in the persistent volume
`staryl-postgres-data`. This will cause the database service to fail to start due to the
data format incompatibility, as no migration logic (like `pg_upgrade`) or initialization
scripts to handle the version change are included.

Did we get this right? 👍 / 👎 to inform future reviews.

container_name: staryl-postgres
image: "postgres:15-alpine"
image: "postgres:18-alpine"
ports:
- "5432:5432"
restart: no
Expand Down
Loading