chore: upgrade to 3.3.0+2.23.2 #4
Reference in New Issue
Block a user
No description provided.
Delete Branch "upgrade-3.3.0+2.23.2"
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?
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