#91

merge queue: merged #90: fix(deps): update postgres docker tag to v19

NOTE

This is a merge queue draft opened by Mergify. Its pull request has merged, and nobody needs to act on it. Mergify opened it for batch coordinated-brie-wdinej of the default queue, to test #90 before it merged into main.

🎉 What landed

Mergify merged its pull request into main, then closed this draft:

  • #90 fix(deps): update postgres docker tag to v19 (renovate[bot]), as dfa8262

This draft's code was built in this order:

  1. main at 42f01cc
  2. #90, the pull request of this batch
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 42f01cc491035b3b872563d86ee94bf6e7964d4f
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 90
    scopes: []
queue_base_sha: 42f01cc491035b3b872563d86ee94bf6e7964d4f
scopes: []
...
Required conditions of queue rule default for merge

No extra conditions.

Required conditions to stay in the queue

None

Confidence Score: 4/5

This PR should not merge until existing PostgreSQL 17 databases have a supported upgrade path.

Findings

  1.  Existing databases cannot start ▶
Fix with agent prompt
### Issue 1
docker-compose.yaml:37
Changing `dbpolitepol` from PostgreSQL 17 to 19 keeps the existing `pol_pg` volume, but PostgreSQL cannot directly open database files created by another major version. Users following the documented `docker compose pull` and `docker compose up -d` upgrade will lose database access. `politepol` also cannot start because it waits for a healthy database.

Keep PostgreSQL 17 until a supported migration and matching upgrade instructions are provided.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This PR changes the Docker database image from PostgreSQL 17 to 19.

  • The Compose database now runs PostgreSQL 19.

Reviews (1) · Last reviewed commit: "Merge of PR 90" · Reviewed by Greptile

Activity

11
M
207ed2e
coderabbitai[bot]5h ago

IMPORTANT

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 124ac47e-6210-462d-ba7d-0cf8affb4ec7

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

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

sourcery-ai[bot]5h ago

Reviewer's Guide

Configuration

Update the PostgreSQL container image tag from version 17 to version 19.

  • docker-compose.yaml L37

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an issue from a review comment by replying to it. You can also reply to a review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull request title to generate a title at any time. You can also comment @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in the pull request body to generate a PR summary at any time exactly where you want it. You can also comment @sourcery-ai summary on the pull request to (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the pull request to resolve all Sourcery comments. Useful if you've already addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull request to dismiss all existing Sourcery reviews. Especially useful if you want to start fresh with a new review - don't forget to comment @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

snyk-io[bot]5h ago

:white_check_mark: Snyk checks have passed. No issues have been found so far.

StatusScan Engine Critical High Medium LowTotal (0)
:white_check_mark:Open Source Security0000 0 issues

:computer: Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

admin changed the title from merge queue: checking #90 on main (42f01cc) to merge queue: merged #90: fix(deps): update postgres docker tag to v195h ago
admin closed this pull request5h ago
codacy-production[bot]5h ago

Up to standards :white_check_mark:

🟢 Issues 0 issues

Results: 0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer TIP This summary will be updated as you push new changes.

greptile-apps[bot]reviewed5h ago
greptile-apps[bot]reviewed5h ago

This pull request was closed without being merged. Branch mergify/merge-queue/82cde968e4 is still available.