n8n 3.0 enters beta with reliability and security changes, plus a Migration Report that flags workflows to fix before upgrading
n8n released the n8n 3.0 beta on October 27, with the stable release expected in early December. The version focuses on reliability, stability and security rather than new features, and it includes breaking changes, so some workflows and settings may need updates. Among the changes: manual executions always run on workers in queue mode, the in-memory binary data mode is removed in favor of the filesystem or S3, the default Code node timeout drops from 5 minutes to 1 minute (and is configurable), and the Cron and Interval nodes are replaced by the Schedule Trigger. On security, encryption key rotation is always on, Slack credentials require a signing secret, and unverified community packages are off by default. Self-hosting is now supported only on Docker, not through npm or npx, while Kubernetes and Helm deployments are not affected. Legacy nodes such as Function, Item Lists, the legacy OpenAI node and older AI Agent modes are removed, and most have a direct replacement. Every instance on version 2.39 or later has a Migration Report in Settings that lists affected workflows, fixes many issues automatically as a new workflow version, and exports a CSV summary. n8n says moving to 3.x is one way with no return to 2.x, so it recommends a full backup and trying a test instance first.
Otomatzia editorial · Published
Source published: · n8n
