Is n8n 2.46.4 safe to update?

Yes, with care. Small patch with bug fixes. Docker users should be fine; if you install n8n with npm -g, watch the open EBADPLATFORM install issue from 2.46.0 before upgrading.

What users are reporting

3 public report(s) mention this version, none clearly describing breakage. Most-discussed: “npm install -g n8n fails with EBADPLATFORM since 2.46.0 (musl-only native bindings are hard dependencies)”. Sources: GitHub · checked 2026-11-03

• npm install -g n8n fails with EBADPLATFORM since 2.46.0 (musl-only native bindings are hard dependencies) (GitHub)
• Top navigation tabs (Workflows / Agents / Credentials...) jitter in Safari, fine in Edge(Chrome) (2.46.x) (GitHub)
• Error encountered when upgrading n8n to 2.46.4 via npm (GitHub, closed)

Reports are from public issue trackers and forums. Their count isn't a failure rate, and an empty list doesn't prove an update is safe.

⚠️ What breaks

Nothing explicitly breaking is flagged, but the notes mention migrations, deprecations or larger changes. Most setups upgrade fine. Back up first and update when you have time to check.

From the release notes

• Release notes: bug fixes only, mostly in the migration report tool (no database migration in this patch).
• Community: open GitHub issue says global npm installs fail with EBADPLATFORM since 2.46.0; Docker images are not affected by that report.

Read the full official release notes →

✅ What to do first

1. Read the official release notes (linked in “What breaks”).
2. Back up config and data (snapshot the VM/volume if you can).
3. Note the version you are on now, so you can roll back.
4. Update, then check logs and core functions before walking away.

↩️ How to roll back to 2.45.7

Docker: snapshot/back up the data volumes first, then if needed change the tag back, e.g. image: n8nio/n8n:2.45.7, and run docker compose up -d. Tag format varies by image (some drop the “v”), so check the registry’s tag list.