Skip to content

Toolsn8n

n8n 2.0 ships secure-by-default workflows and a separate Publish step

n8n 2.0 at a glance

n8n released version 2.0 in beta on December 8, 2025, with isolated Code node execution, stricter defaults, and a Save/Publish split; the stable 2.0.x line followed on December 15.

What changed with n8n 2.0

n8n 2.0 focuses on security, reliability, and performance rather than new nodes. Task runners are on by default, so Code node executions run in isolated environments, environment variables are blocked from Code nodes, and nodes that can run arbitrary commands are disabled unless an admin turns them back on.

Saving an active workflow no longer changes production: Save keeps your edits and a separate Publish action updates the live version. n8n also cites a new SQLite pooling driver that was up to 10x faster in its own benchmarks, and a Migration Report under Settings that lists issues to fix before upgrading.

Why n8n 2.0 matters for businesses

Version 1.x receives only security and bug fixes for three months after the 2.0 release. Teams that self-host client automations should run the Migration Report and plan upgrades, since the new defaults can break workflows that relied on environment variables or command-execution nodes.

Put it to work: AI Automations

Sources for this story

  1. Official

Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.

  • #n8n
  • #workflow-automation
  • #security
  • #self-hosting

Want this working in your business?

We turn new AI capabilities into agents, voice receptionists, and automations you can actually use.