n8n v2

What changed — and why it matters

n8n 2.0 launched in beta on December 8, 2025 and reached stable release on December 15 — the platform's first major version increment since 1.0 in July 2023. The release is what the n8n team describes as a "hardening release": its purpose is not to add capabilities but to make the platform more secure, more stable, and more suitable for production environments. The official announcement is explicit on this: n8n follows semantic versioning, meaning breaking changes are held until a major version bump. Version 2.0 ships the security and reliability improvements that have been accumulating since 1.0.

This distinction matters for teams evaluating whether to upgrade: v2.0 is not a feature release. Existing workflows will largely continue to function, but some configurations — particularly Code nodes that accessed environment variables directly — will behave differently by default.

The Save / Publish separation

In v1.x, saving an activated workflow immediately updated the live production environment. In v2.0, the Save button preserves edits without touching what is running in production. A separate Publish action explicitly pushes changes live. The release notes describe this as a "safer approach to updating live workflows" — particularly relevant for teams running workflows that process inbound leads, health score alerts, or reporting pipelines continuously.

For teams that have previously experienced accidental production disruptions from a mis-saved workflow, this change eliminates that category of error. It also prepares the platform for the autosave feature planned for January 2026.

Task Runners and process isolation

The most significant architectural change is Task Runners enabled by default. Code nodes — JavaScript and Python — now run in isolated processes rather than in the main n8n instance. Previously, a memory leak or infinite loop in a Code node could bring down the entire instance. With v2.0, a failing Code node is contained within its own process. This is what makes v2.0 meaningfully more suitable for teams running n8n in shared or production environments where uptime matters.

v1.x will receive security updates for three months post-release, after which all new features and fixes will be v2.0 only. The n8n documentation includes a migration tool that scans existing workflows for compatibility issues before upgrade — checking Code nodes, environment variable access patterns, and deprecated features.

Nuevexa builds and maintains production automation workflows on n8n, including migrations from v1.x to v2.0. See our Workflow Automation service for how we architect and maintain n8n deployments for growing operations teams.