Files
cc-ci-orchestrator/cc-ci-plan/upstream/n8n.md

22 lines
1.6 KiB
Markdown

# Upstream sources — n8n
| service | image | source repo | releases / changelog |
|---------|-------|-------------|----------------------|
| app | n8nio/n8n | https://github.com/n8n-io/n8n | https://github.com/n8n-io/n8n/releases |
| db | pgautoupgrade/pgautoupgrade | https://github.com/pgautoupgrade/pgautoupgrade | https://hub.docker.com/r/pgautoupgrade/pgautoupgrade/tags |
## Standing notes
- pgautoupgrade uses a non-standard tag scheme (e.g. `17-alpine`, `18-alpine`) mapping to the TARGET
Postgres major version. `18-alpine` = upgrade-on-start to Postgres 18. The compose.postgres.yml
controls this image; the main compose.yml uses only `n8nio/n8n` (sqlite mode).
- n8n 2.x: standard rolling upgrade is safe between 2.x versions; DB migrations run automatically on startup.
Confirmed live on cc-ci 2026-07-15 (2.27.2 -> 2.31.0, sqlite mode): all TypeORM migrations completed
cleanly on boot, editor served HTTP 200 immediately after.
- The n8n Docker image on Docker Hub uses plain semver tags (e.g. `2.25.3`); no `-stable` suffix needed.
- `https://docs.n8n.io/release-notes/` now 404s (checked 2026-07-15) -- n8n appears to have dropped the
docs-site changelog. Use GitHub Releases instead: https://github.com/n8n-io/n8n/releases (tag format
`n8n@<version>`, e.g. `n8n@2.31.0`) -- this is the canonical source now.
- 2.31.0 shipped "private credentials enabled by default" (UI renamed to "end-user credentials") and a
Notion node API migration -- functional/UX changes worth a heads-up to the operator, not deployment
blockers (no compose/env/migration impact).