chore: upgrade pgautoupgrade from 16-alpine to 17-alpine #2
Reference in New Issue
Block a user
No description provided.
Delete Branch "upgrade-84736c1"
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?
hedgedoc: upgrade pgautoupgrade 16-alpine → 17-alpine
Image changes
What changed
hedgedoc 1.10.8 → 1.11.0 (already published as 3.1.0+1.11.0 by upstream):
Upstream release notes: hedgedoc 1.10.8→1.11.0: https://github.com/hedgedoc/hedgedoc/releases/tag/1.11.0
pgautoupgrade 16-alpine → 17-alpine:
Upstream release notes: pgautoupgrade: https://github.com/pgautoupgrade/pgautoupgrade/releases
Operator Action Required
None — security patch + infrastructure bump, no breaking changes.
After upstream PR merges, publish the new patch release:
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
hedgedoc@84736c14✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.