Agentic WeeklyGet the weekly

n8n 3.0 beta is out: Docker-only self-hosting, legacy nodes removed, stable in early December

Release Ruler for this brief: marked at its publication date, Oct 27, 2026, among the AI models we track.

n8n released version 3.0.0 as a beta on October 27, 2026, with the stable release planned for early December; it is a breaking-change release focused on reliability and security, self-hosted n8n now runs only on Docker, and the upgrade from 2.x cannot be rolled back, so n8n recommends running the Migration Report (version 2.39 or later) and taking a full backup first.

By Agentic Weekly · Evidence: Reported · How we work

First seen
(via n8n blog)
Source published
(we saw it 12 minutes later)
Brief published

What changed

  • n8n 3.0.0 is available as a beta from October 27, 2026; the n8n blog says the stable release follows in early December and that 3.0 bundles breaking changes rather than new features.
  • Self-hosted n8n now runs on Docker: installing with npm or npx n8n is no longer supported, which n8n says is partly because new security features depend on a container setup. Kubernetes and Helm deployments are not affected.
  • Removed legacy nodes include Function, Function Item, Item Lists, Cron, Interval, the legacy OpenAI node and older AI Agent modes; Function maps to the Code node and Cron and Interval to the Schedule Trigger. Chat Hub is off by default and Import from URL is gone from the editor.
  • Safer defaults: encryption key rotation is always on, Slack credentials require a signing secret, the SSRF block list is larger when SSRF protection is enabled, unverified community packages are off, and the default Code node timeout drops from 5 minutes to 1 minute.
  • Runtime changes: in queue mode, manual executions always run on workers, and the in-memory binary data mode is removed in favour of the filesystem or S3 and other external storage.
  • Upgrading is one way, with no rollback to 2.x. Instances on 2.39 or later have a Migration Report under Settings that lists affected workflows, auto-fixes many as new workflow versions, and exports a CSV. 2.x gets security and critical fixes for 12 months after stable; 1.x support ends December 31, 2026.

In the source’s words

“moving to 3.x is one way. There's no going back to 2.x.”

“Installing with npm or npx n8n is no longer supported, partly because new security features depend on a container setup.”

Early verdict

Self-hosters on npm installs or using Function, Cron or legacy OpenAI nodes should run the Migration Report and test on a staging instance before moving to 3.x, since the upgrade cannot be reversed.

Basis: Based only on the changes and upgrade path n8n's announcement describes; we have not run the beta.

What we have not verified

  • We did not install the beta or run the Migration Report ourselves.
  • We read the announcement post only; the full per-change list is in n8n's breaking changes docs, which we did not review item by item.
  • The exact stable release date is given only as early December.

This brief is Reported: written from the sources below, not from running the release ourselves.

Sources

Spotted an error? See our corrections policy or email the address on the contact page. Markdown version for agents: /news/n8n-3-0-beta-breaking-changes.md

Want these briefs in your Google Top Stories? Add Agentic Weekly as a preferred source on Google.