cc-ci-orchestrator/cc-ci-plan/upstream/hedgedoc.md

Upstream sources — hedgedoc

service	image	source repo	releases / changelog
app	quay.io/hedgedoc/hedgedoc	https://github.com/hedgedoc/hedgedoc	https://github.com/hedgedoc/hedgedoc/releases
db	pgautoupgrade/pgautoupgrade	https://github.com/pgautoupgrade/docker-pgautoupgrade	https://github.com/pgautoupgrade/docker-pgautoupgrade/commits/main (no GitHub releases; tag-only)

Standing notes

• hedgedoc 1.11.0 (2026): 4 security CVEs fixed (HTML injection, YAML DoS, CSRF via Gist export, rate-limit bypass). No breaking changes, no migrations, no schema changes. Optional new env var CMD_RATE_LIMIT_USING_CLOUDFLARE only needed if running behind Cloudflare — not required for standard deployments.
• pgautoupgrade: handles Postgres major-version upgrades automatically on container start. Bump ONE major at a time (16→17, then 17→18 on next cycle). The image tag is <pg-major>-alpine.
• pgautoupgrade 18+ (deferred, learned 2026-09-11): PG 18 changes the data-directory layout (docker-library/postgres#1259; PGDATA → /var/lib/postgresql/<MAJOR>/docker) — this recipe mounts postgres:/var/lib/postgresql/data with no PGDATA, and per the pgautoupgrade README ("Error message when mounting data to /var/lib/postgresql/data on Postgres v18+") that needs a dedicated PGDATA/volume-mount change before bumping to 18, or you can get an empty instance instead of an upgraded one. 16→17 verified live on cc-ci 2026-09-11 (Upgrade to PostgreSQL 17.11 complete., data survived).
• hedgedoc 1.12.0 (2026-08): requires Node 20.17+ (app image bundles its own node — not recipe-relevant); webp uploads; some highlight.js languages removed/changed. No breaking changes or migrations for the recipe.
• cc-ci tests use the sqlite backend (default compose.yml), not the postgresql compose override — so pgautoupgrade bumps do not affect CI test coverage (verify pg bumps via a direct --chaos deploy with the postgresql override instead).