n8n 3.0 beta lands October 27: what n8n announced

n8n has set dates for its next major version: the n8n 3.0.0 beta arrives on October 27, 2026, and a stable 3.x release follows in early December. The upgrade is one way, with "no going back to 2.x afterwards." n8n 2.x keeps getting security and critical bug fixes for 12 months after the stable release, and support for 1.x ends on December 31, 2026.

The dates come from an announcement on n8n's community forum, posted on October 23 by a member of n8n's product marketing team. As of October 24, n8n's 3.0 breaking changes page still says only that 3.0 "is releasing soon," and npm shows stable 2.44.6 and beta 2.45.3.

The short version

• It's one way. n8n recommends testing 3.0 on a non-production instance and taking a full backup first.
• 1.x can't jump to 3.x. Upgrade to 2.x first.
• New features go to 3.x only once the stable release is out; 2.x gets fixes, not features.
• Kubernetes and Helm setups aren't affected by the end of npm installs. Self-hosted n8n otherwise needs Docker.
• n8n Cloud gets an opt-in: choose 3.0.0 Beta (early access) when you change your n8n version.

What n8n 3.0 is about

The announcement describes 3.0 as a release about "reliability, stability, and security," with most changes under the hood. It doesn't add big new features. Instead, it collects the breaking changes n8n has queued up over the past year, and future features will ship on 3.x. The main changes it lists:

• Legacy nodes removed, including Function, Function Item, Item Lists, Cron, Interval and the legacy OpenAI node.
• Stricter security defaults, such as encryption key rotation on by default and a required signing secret for Slack credentials.
• Docker required for self-hosting. Installs with npm or npx n8n are no longer supported.
• Chat Hub off by default (you can turn it back on in 3.x), and Import from URL removed from the editor.

Our n8n 3.0 breaking changes guide covers every change and its fix. It also includes two changes from n8n's code that its docs page doesn't list yet: an enforced Content-Security-Policy and always-on workflow tags.

You can't roll back to 2.x

The most important line in the announcement: moving to 3.x is one way, and "there's no going back to 2.x afterwards."

When we upgraded a 2.x instance to a 3.0 nightly build on October 18, pointing it back at 2.43.7 still worked. That was a preview build, and n8n's statement now settles the question for the real release: don't plan on running 2.x against data that 3.x has touched. Your rollback is the backup you take before the upgrade, restored into the old version. Our one-way upgrade guide has a tested backup, restore test and rollback procedure. Our guide on how to update self-hosted n8n safely has the backup and restore commands.

How to prepare before October 27

n8n's recommended path, from the announcement:

1. Update to the latest 2.x. For production, that's the stable release, 2.44.6.
2. Open Settings > Migration Report (available from n8n 2.39). Fix each flagged item, or mark it as won't fix.
3. Take a full backup.
4. Upgrade a staging instance first, then production.

Two details about the Migration Report make this easier than for 2.0:

• It isn't admin-only anymore. Every user sees the findings for the workflows they can access, and admins can assign workflows to their owners, who get an email listing what to fix.
• Many fixes can be applied for you. In the announcement's words, "each fix is saved as a new workflow version," which you review and publish. When we tested the automatic Cron migration in our n8n 2.45 roundup, the published version kept the old node until we republished, so don't skip the publish step.

If you run n8n with npm or npx, move to Docker on your current 2.x version before you touch 3.0; our Docker Compose guide has a tested setup.

How to try the beta

• n8n Cloud: choose 3.0.0 Beta (early access) when you change your n8n version.
• Self-hosted: the announcement doesn't name the beta's Docker tag. Don't expect it on npm, because 3.0 "doesn't publish a runnable n8n package to npm," per n8n's breaking changes page. Check Docker Hub on October 27, and pin the exact tag in a copy of your instance, never production.

Until the beta is out, the weekly v3-rc and daily v3-nightly images are the closest preview. Our nightly test shows what to expect, including the 60-second Code node timeout that needs raising on both the n8n and task runner containers.

We will test the 3.0.0 beta when it ships on October 27 and report what changed. For all release coverage, see the releases tag.