According to an official announcement published by n8n, n8n version 3.0.0 BETA has been released, with the stable release scheduled to arrive in early December. The announcement post stated that version 3.0 focuses on internal changes designed to improve reliability, stability, and security, laying the groundwork for the system's upcoming developments. The update removes legacy features, tightens default security settings, and reworks parts of how n8n operates at the internal infrastructure level. Because the release includes breaking changes, certain workflows and settings may require adjustments and updates before performing the upgrade.
Reasons for the Major Version Update and the Feature Release Model
At n8n, they explain that the platform operates on a semantic versioning model. This means that the company does not ship breaking changes—updates that might require modifying workflows or configuration settings—without bumping the major version number. Over the past year, a list of breaking changes was accumulated, including the removal of legacy code paths, making defaults safer, and deprecating several features. Each of these changes had to wait for a major version, which is why version 3.0 brings them together into a single release.
According to the company, new features do not wait for major versions, as n8n ships features continuously. Since the release of version 2.0 in December 2025, the company has issued over 45 releases, at a pace of roughly one release per week, with many of them including major new features detailed in the changelog. Consequently, version 3.0 can focus purely on the underlying foundation, while new developments will be shipped in 3.x releases following the launch of the stable version.
Reliability and Stability Improvements in System Infrastructure
The breaking changes documentation for version 3.0 outlines several key areas of stability and reliability:
- Queue mode: Manual executions now always run on workers, so the main instance does not perform this work itself.
- Binary data: The in-memory binary data mode has been removed. Instances now use the local filesystem, or S3 and other external storage, providing more predictable behavior under load.
- Guardrails against runaway work: The default timeout for the Code node in the task runner drops from 5 minutes to 1 minute, and it is configurable. In addition, decompression limits are lower, aimed at protecting instances from oversized archives ("zip bombs").
- Scheduling: The legacy Cron and Interval nodes are replaced by the Schedule Trigger, which runs on n8n's more durable scheduler engine.
Tightening Security Defaults
In version 3.0, several safer defaults have been established:
- Encryption key rotation is now always set to active.
- Slack credentials require the use of a signing secret, preventing the ability to send forged requests impersonating Slack.
- The default blocklist for SSRF (server-side request forgery) has been expanded when SSRF protection is enabled.
- Unverified community packages are disabled by default.
Self-Hosting Changes and Removal of npm Support
For users running the platform in a self-hosted installation, n8n 3.0 now operates on Docker. Installing via npm or running using npx n8n is no longer supported, partly because new security features depend on a container-based setup. For users who preferred using npx n8n due to its quick startup, the company provides a one-line setup script that achieves the same result. Deployments based on Kubernetes and Helm are not affected by this change.
Removal of Legacy Components and Feature Retirement
Version 3.0 removes a series of legacy nodes, including: Function, Function Item, Item Lists, Cron, Interval, the legacy OpenAI node, older AI Agent modes, older versions of the Edit Image node, and nodes designed for services that no longer exist. A significant portion of them have direct replacements (Function is replaced by the Code node; Item Lists is replaced by Split Out, Aggregate, Sort, Limit, Remove Duplicates, or Summarize), and many of them migrate automatically.
In addition, several features have been retired: the Chat Hub feature is turned off by default (it can be re-enabled for 3.x releases, as the n8n AI assistant and agents replace it), the Import from URL option has been removed from the editor, and the Ask AI tab has been removed from the Code node.
The Migration Report and Upgrade Recommendations
According to the announcement, every instance on version 2.39 or later includes a dedicated Migration Report under the settings menu (Settings > Migration Report). The latest 2.x version contains the newest edition of the report. The report maps the workflows and instance-level settings affected by version 3.0 and fixes many issues automatically. Each fix is saved as a new workflow version for review and publication, while published workflows continue running on version 2 while changes are being made.
Furthermore, the report suggests an owner for each workflow (the person who edited it last), allows administrators to reassign ownership, and emails owners with details of the required fixes. The report filters out workflows that are unpublished or have not run in a long time (which can be marked as "won't fix"), and enables exporting a summary in CSV format. Administrators see all workflows, and other users see those they have access to, without requiring administrative permissions to view the report.
The recommended upgrade path includes updating to the latest 2.x version, reviewing the Migration Report and addressing the issues flagged in it, taking a full backup, and upgrading a test or staging environment before upgrading production. Moving to version 3.x is one-way, and there is no option to roll back to version 2.x without restoring from a backup.
Activity Metrics, Support, and Timelines
The post noted that since the release of version 2.0, the number of n8n GitHub stars grew from approximately 160,000 to over 208,000, and the count of community forum members increased from 115,192 to over 183,000.
Regarding timelines and support for prior versions: the beta version (3.0.0) is available as of October 27, and the stable release will arrive in early December. Following the release of the stable version, version 2.x will continue to receive security fixes and critical bug fixes for 12 months, while new features will be released only for 3.x versions. For users who are still on version 1.x, an upgrade to version 2.x is required first because there is no direct upgrade path from 1.x to 3.x; support for version 1.x will conclude on December 31, 2026. All changes in version 3.0 apply to self-hosted Community editions, Cloud editions, and Enterprise/Business editions. Credentials and execution history are preserved during the transition.