From e89884beba4863d9e6478864ed720d176978ead1 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Fri, 12 Jun 2026 04:12:32 +0000 Subject: [PATCH] upstream(n8n): update standing notes for 2.26.3 upgrade --- cc-ci-plan/upstream/n8n.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cc-ci-plan/upstream/n8n.md b/cc-ci-plan/upstream/n8n.md index c3a6d77..b610c29 100644 --- a/cc-ci-plan/upstream/n8n.md +++ b/cc-ci-plan/upstream/n8n.md @@ -9,6 +9,6 @@ - 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: no breaking DB migrations between 2.23.2 and 2.25.3; standard rolling upgrade is safe. +- n8n 2.x: standard rolling upgrade is safe between 2.x versions; DB migrations run automatically on startup. - The n8n Docker image on Docker Hub uses plain semver tags (e.g. `2.25.3`); no `-stable` suffix needed. - n8n release notes: https://docs.n8n.io/release-notes/