build(deps): bump postgres from 14.23-bookworm to 18.4-bookworm#4413
build(deps): bump postgres from 14.23-bookworm to 18.4-bookworm#4413dependabot[bot] wants to merge 1 commit into
Conversation
Bumps postgres from 14.23-bookworm to 18.4-bookworm. --- updated-dependencies: - dependency-name: postgres dependency-version: 18.4-bookworm dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 786570e. Configure here.
| <<: *restart_policy | ||
| # Using the same postgres version as Sentry dev for consistency purposes | ||
| image: "postgres:14.23-bookworm" | ||
| image: "postgres:18.4-bookworm" |
There was a problem hiding this comment.
Missing Postgres major version migration
High Severity
Switching the postgres service to postgres:18.4-bookworm is a major-version jump from 14.x. PostgreSQL cannot open an existing 14 cluster on disk without pg_upgrade or dump/restore, and install/upgrade-postgres.sh only migrates 9.6 volumes. Upgrades and CI volume restores with sentry-postgres data are likely to leave Postgres unhealthy and block install.sh.
Reviewed by Cursor Bugbot for commit 786570e. Configure here.
|
@dependabot ignore this dependency |
|
Sorry, only users with push access can use that command. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |


Bumps postgres from 14.23-bookworm to 18.4-bookworm.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)