upstream(n8n): 3.x breaking-change notes + live 2.45.2->3.3.0 validation
This commit is contained in:
@@ -386,3 +386,35 @@
|
||||
unverified-packages default, runner-timeout/compression-limit default reductions). Advisory scan
|
||||
2.40.5→2.45.2: 0 CVEs identified, BUT the GitHub advisory sources failed (unauthenticated rate
|
||||
limit) — scan incomplete, not to be read as clean. Recommended release: `-y`.
|
||||
- 2.48.3–2.48.6 (2026-11-xx, stable line — `stable`/`latest` floating tags point at 2.48.6 as of
|
||||
2026-11-20): patches/fixes on the 2.48 line; 2.48.3 fixed **CVE-2026-130167 (high)**.
|
||||
- 2.49.0–2.49.2 (2026-11-17..19, Pre-release/beta — `beta`/`next` floating tags = 2.49.2): the next
|
||||
beta minor line; not taken (3.x line was the run's target).
|
||||
- **3.0.0 (2026-10-27) — MAJOR breaking release** (early access; all 3.x releases marked
|
||||
`prerelease=true` on GitHub): see https://docs.n8n.io/changelog/v30-breaking-changes.md — removed
|
||||
legacy nodes (Function/Item Lists/Cron/Interval/HTML Extract/legacy OpenAI/etc.), AI Agent v1
|
||||
modes, `$getPairedItem`/`$evaluateExpression()` helpers, in-memory binary-data mode
|
||||
(`N8N_DEFAULT_BINARY_DATA_MODE=default` auto-switches to filesystem), env-var removals
|
||||
(N8N_PRE_EXECUTE_ERROR_CREATES_EXECUTION, N8N_DB_PING_TIMEOUT, N8N_WORKFLOW_TAGS_DISABLED,
|
||||
OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS), storage dir renamed `~/.n8n/binaryData` → `~/.n8n/storage`
|
||||
(refuses to start if BOTH exist; auto-rename otherwise), unverified community packages off by
|
||||
default, runner timeout 300→60s, compression limits reduced, Slack credential signing-secret
|
||||
required, Chat Hub off by default, encryption-key rotation on by default, npm/npx installs no
|
||||
longer supported (Docker only). No staged upgrade path demanded; DB migrations auto-run.
|
||||
- 3.1.0/3.2.0/3.3.0 (2026-11-03/10/17): bugfix releases, no further breaking changes; 3.2.0 added
|
||||
removed-mode detection hardening; 3.2.2 also fixes CVE-2026-130167 (fixed >= 2.48.3 on 2.x line).
|
||||
- 2026-11-20 run: PR #10 (branch `upgrade-da8a15f`, at 2.48.2) extended **2.45.2 → 3.3.0** on
|
||||
upstream main `babcb72` (upstream main still pins 2.45.2 — n8n never merged the PR lineage).
|
||||
Compatibility check: no staged path, recipe env compatible (sets none of the removed vars), no
|
||||
queue mode, sqlite default. **Live-validated on cc-ci dev deploy**: published 3.5.2+2.45.2 with a
|
||||
real owner account (POST /rest/owner/setup — the 2.45.2 setup endpoint; `/rest/owner` is 404)
|
||||
+ marker file, then `--chaos` redeploy to 3.3.0: all TypeORM migrations clean
|
||||
(through `AddAgentFolderPlacement1794826383663`), `Recorded version change: 2.45.2 -> 3.3.0`,
|
||||
`/healthz` 200, owner login 200 after migration, marker survived, `storage` dir created with no
|
||||
`binaryData` conflict. Gotchas this run: (1) any abra call (e.g. `abra app new`'s recipe fetch)
|
||||
can hard-reset the recipe checkout — re-`git reset --hard <work-commit>` before `--chaos` deploy
|
||||
if the checkout was reset; (2) image for the dev app service is
|
||||
`dev-n8n_ci_commoninternet_net_app` (leading dash). Advisory scan 2.45.2→3.3.0: 1 CVE fixed
|
||||
(CVE-2026-130167) + 15 GHSAs fixed; GHSA-365g-vjw2-grx8 (high) open by design (Execute Command
|
||||
node; no patch — mitigate via `NODES_EXCLUDE`). `!testme` GREEN (build 168). Recommended
|
||||
release: `-x` (major).
|
||||
|
||||
Reference in New Issue
Block a user