chore(deps): update pgautoupgrade/pgautoupgrade docker tag to v18 #85

2026-06-10T10:17:39Z

renovate-bot commented

2026-06-10 10:17:39 +00:00

This PR contains the following updates:

Package	Update	Change
pgautoupgrade/pgautoupgrade	major	`14-debian` -> `18-debian`

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | pgautoupgrade/pgautoupgrade | major | `14-debian` -> `18-debian` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

renovate-bot added 1 commit 2026-06-10 10:17:40 +00:00

chore(deps): update pgautoupgrade/pgautoupgrade docker tag to v18

continuous-integration/drone/pr Build is failing

Details

07185ef4e9

ineiti commented

2026-07-25 19:43:40 +00:00

Is anybody using postgresql and can test if this works?

ineiti added the help wanted label 2026-07-25 19:44:03 +00:00

maren commented

2026-07-28 20:07:23 +00:00

First-time contributor

We are using postgresql and have had some issues with the change that preceded this, from the upstream postgres image to the autoupgrade container. one thing that will certainly break here is that the mount path for the data volume changes in version 18, from /var/lib/postresql/data to var/lib/postgresql

this is also a sudden update across 4 major versions of postgres, which historically does not update across versions easily (which is what motivated the change to the autoupgrade container). i think it's too big of an update.

is there a precedent for other recipes when they update their database versions? we do need to update the postgres container, but i'd like to have more of a plan than just allowing renovated bot to bump us 4 versions.

We are using postgresql and have had some issues with the change that preceded this, from the upstream postgres image to the autoupgrade container. one thing that will certainly break here is that the mount path for the data volume changes in version 18, from /var/lib/postresql/data to var/lib/postgresql this is also a sudden update across 4 major versions of postgres, which historically does not update across versions easily (which is what motivated the change to the autoupgrade container). i think it's too big of an update. is there a precedent for other recipes when they update their database versions? we do need to update the postgres container, but i'd like to have more of a plan than just allowing renovated bot to bump us 4 versions.

continuous-integration/drone/pr Build is failing

Details

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/pgautoupgrade-pgautoupgrade-18.x:renovate/pgautoupgrade-pgautoupgrade-18.x

git checkout renovate/pgautoupgrade-pgautoupgrade-18.x

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#85