recipe-maintainers/hedgedoc
0
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore: upgrade pgautoupgrade from 16-alpine to 17-alpine #3

Open
autonomic-bot wants to merge 1 commits from upgrade-341922a into main
pull from: upgrade-341922a
merge into: recipe-maintainers:main
Conversation 2 Commits 1 Files Changed 1 +1 -1
autonomic-bot commented 2026-06-22 21:37:31 +00:00
Owner
Copy Link

Recipe upgrade — bump PostgreSQL sidecar (pgautoupgrade) one major version: 16-alpine → 17-alpine.

HedgeDoc app image (quay.io/hedgedoc/hedgedoc:1.11.0) is up-to-date per abra recipe upgrade and left untouched.

Image tag table

service current new file
db (postgresql overlay) pgautoupgrade/pgautoupgrade:16-alpine pgautoupgrade/pgautoupgrade:17-alpine compose.postgresql.yml

Upstream release notes

Recipe version bump

Patch (-z): a sidecar infrastructure bump (Postgres major via pgautoupgrade), no app change, no recipe-level breaking change. The PR does NOT bump the coop-cloud.${STACK_NAME}.version label — the operator publishes the new release at merge time:

abra recipe release hedgedoc -z

Operator action required

  • Existing postgres-overlay deployments: pgautoupgrade runs pg_upgrade automatically on next deploy (16 → 17). Plan a brief maintenance window (one-time upgrade, seconds-to-minutes depending on DB size). Back up the postgres volume before deploying — the recipe already wires backupbot.backup hooks, so operators using backup-bot are covered.
  • New deployments / default sqlite-backend deployments: no action.

Direct-deploy verification (cc-ci dev swarm)

Deployed the WIP compose.postgresql.yml overlay under dev-hedgedoc.ci.commoninternet.net and exercised a real pg_upgrade (2-phase deploy): first deployed 16-alpine to seed a PG-16 datadir on the volume, then redeployed 17-alpine on the SAME volume — pgautoupgrade detected the older datadir and ran pg_upgrade: "Upgrade to PostgreSQL 17.10 complete." Hedgedoc then connected to the upgraded PG-17 instance, confirmed schema intact (All migrations performed successfully — no missing migrations, indicating data was preserved through the major upgrade), and served HTTPS 200. The dev deploy was then torn down (0 leaked stacks / volumes).

This is a re-attempt of the same 16→17 bump from 2026-06-19 (PR #2, !testme GREEN on drone build 931), which the operator closed without merging; upstream main still has 16-alpine, so a fresh upgrade PR is opened here.

NOT merged — for operator review.

Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.

cc @trav @notplants

Recipe upgrade — bump PostgreSQL sidecar (pgautoupgrade) one major version: 16-alpine → 17-alpine. HedgeDoc app image (`quay.io/hedgedoc/hedgedoc:1.11.0`) is up-to-date per `abra recipe upgrade` and left untouched. ### Image tag table | service | current | new | file | |---|---|---|---| | db (postgresql overlay) | `pgautoupgrade/pgautoupgrade:16-alpine` | `pgautoupgrade/pgautoupgrade:17-alpine` | `compose.postgresql.yml` | ### Upstream release notes - **db** pgautoupgrade 16-alpine → 17-alpine: https://github.com/pgautoupgrade/pgautoupgrade/releases - PostgreSQL 17 release notes: https://www.postgresql.org/docs/17/release-17.html - HedgeDoc app (unchanged; 1.11.0): https://github.com/hedgedoc/hedgedoc/releases ### Recipe version bump Patch (`-z`): a sidecar infrastructure bump (Postgres major via `pgautoupgrade`), no app change, no recipe-level breaking change. The PR does NOT bump the `coop-cloud.${STACK_NAME}.version` label — the operator publishes the new release at merge time: ``` abra recipe release hedgedoc -z ``` ### Operator action required - **Existing postgres-overlay deployments**: `pgautoupgrade` runs `pg_upgrade` automatically on next deploy (16 → 17). Plan a brief maintenance window (one-time upgrade, seconds-to-minutes depending on DB size). Back up the `postgres` volume before deploying — the recipe already wires `backupbot.backup` hooks, so operators using backup-bot are covered. - **New deployments / default sqlite-backend deployments**: no action. ### Direct-deploy verification (cc-ci dev swarm) Deployed the WIP `compose.postgresql.yml` overlay under `dev-hedgedoc.ci.commoninternet.net` and exercised a **real `pg_upgrade`** (2-phase deploy): first deployed `16-alpine` to seed a PG-16 datadir on the volume, then redeployed `17-alpine` on the SAME volume — pgautoupgrade detected the older datadir and ran `pg_upgrade`: *"Upgrade to PostgreSQL 17.10 complete."* Hedgedoc then connected to the upgraded PG-17 instance, confirmed schema intact (`All migrations performed successfully` — no missing migrations, indicating data was preserved through the major upgrade), and served HTTPS 200. The dev deploy was then torn down (0 leaked stacks / volumes). This is a re-attempt of the same 16→17 bump from 2026-06-19 (PR #2, `!testme` GREEN on drone build 931), which the operator closed without merging; upstream main still has `16-alpine`, so a fresh upgrade PR is opened here. NOT merged — for operator review. Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review. cc @trav @notplants
autonomic-bot added 1 commit 2026-06-22 21:37:31 +00:00
chore: upgrade pgautoupgrade from 16-alpine to 17-alpine
All checks were successful
cc-ci/testme cc-ci: success
Details
341922a2df
autonomic-bot requested review from trav 2026-06-22 21:37:32 +00:00
autonomic-bot requested review from notplants 2026-06-22 21:37:32 +00:00
autonomic-bot commented 2026-06-22 21:37:37 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-22 21:37:45 +00:00
Author
Owner
Copy Link

🌻 cc-ci — hedgedoc @ 341922a2 ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `hedgedoc` @ `341922a2` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/950/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/950) [![level](https://ci.commoninternet.net/runs/950/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/950) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/950) · [dashboard](https://ci.commoninternet.net/)
All checks were successful
cc-ci/testme cc-ci: success
Details
This pull request can be merged automatically.
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 upgrade-341922a:upgrade-341922a
git checkout upgrade-341922a
Sign in to join this conversation.
Reviewers
No Reviewers
trav
notplants
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
autonomic autonomic-bot notplants trav
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/hedgedoc#3
No description provided.
Delete Branch "upgrade-341922a"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?