No breaking changes for Docker Compose operators across this range. Versions 2.21–2.23 contain bug fixes, performance improvements, and new features (MCP support, insights improvements) that are backward compatible.
The volume mount path changes from /var/lib/postgresql/data → /var/lib/postgresql (required by pg18+ data directory structure change).
The pgautoupgrade image will automatically detect the old PG17 data and run pg_upgrade on first container start — take a database backup before upgrading.
Without the volume path change, pg18 would not find the existing data.
Recipe version bump
3.2.0+2.20.6 → 3.3.0+2.23.2 (minor bump: volume mount path change is a behavioural change for existing postgres deployments)
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
## n8n upgrade: 3.2.0+2.20.6 → 3.3.0+2.23.2
### Image changes
| Service | Current | New |
|---------|---------|-----|
| `n8nio/n8n` | `2.20.6` | `2.23.2` |
| `pgautoupgrade/pgautoupgrade` | `17-alpine` | `18-alpine` |
### n8n 2.20.6 → 2.23.2
No breaking changes for Docker Compose operators across this range. Versions 2.21–2.23 contain bug fixes, performance improvements, and new features (MCP support, insights improvements) that are backward compatible.
### pgautoupgrade 17-alpine → 18-alpine (PostgreSQL 17 → 18)
**Operator Action Required:**
- The volume mount path changes from `/var/lib/postgresql/data` → `/var/lib/postgresql` (required by pg18+ data directory structure change).
- The `pgautoupgrade` image will automatically detect the old PG17 data and run `pg_upgrade` on first container start — **take a database backup before upgrading**.
- Without the volume path change, pg18 would not find the existing data.
### Recipe version bump
`3.2.0+2.20.6` → `3.3.0+2.23.2` (minor bump: volume mount path change is a behavioural change for existing postgres deployments)
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
n8n upgrade: 3.2.0+2.20.6 → 3.3.0+2.23.2
Image changes
n8nio/n8n2.20.62.23.2pgautoupgrade/pgautoupgrade17-alpine18-alpinen8n 2.20.6 → 2.23.2
No breaking changes for Docker Compose operators across this range. Versions 2.21–2.23 contain bug fixes, performance improvements, and new features (MCP support, insights improvements) that are backward compatible.
pgautoupgrade 17-alpine → 18-alpine (PostgreSQL 17 → 18)
Operator Action Required:
/var/lib/postgresql/data→/var/lib/postgresql(required by pg18+ data directory structure change).pgautoupgradeimage will automatically detect the old PG17 data and runpg_upgradeon first container start — take a database backup before upgrading.Recipe version bump
3.2.0+2.20.6→3.3.0+2.23.2(minor bump: volume mount path change is a behavioural change for existing postgres deployments)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 —
n8n@0abac7df✅ passedfull logs · dashboard
Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced
Pull request closed