n8n, the workflow automation tool, shipped v3.0 as a pre-release. Here are four things from the release notes to check before you move.
n8n is a workflow automation tool that connects services so that routine work runs by itself. It has 75,008 weekly downloads on npm.
n8n v3.0.0 came out on 2026-10-27. Its GitHub release page marks it as a pre-release. v2.46.0 came out the same day.
What stands out in these release notes is not a new node but the tooling that helps you move: the migration report.
Image: github.com
From the v3.0.0 release notes, these are the items that look like they affect the move.
- The LangChain Code node. It is a removed node, and a fix to detect it during the v3 migration went in
- The Edit Image node. A new v2 arrives and the older versions are removed. An entry for the v3 migration of this node was added too
- The Slack signature secret. Migration rules for it were added for v3
- The impact items of the report. The migration report gained an "Executions might fail" impact
The migration report tells you in advance where your workflows would catch on v3. These are the features this release adds to it.
- The report can be exported as CSV
- Workflow editors can triage the findings of their own workflows
- The workflows in the report can be filtered by project
- In the editor, the report's documentation link points to the v3 breaking changes page
Image: n8n-io
Because v3.0.0 is a pre-release, it is not a version to move a production server to right away. There is something to do now, though: put the pre-release in a separate environment and open the migration report first.
- Look in the report for workflows that use the LangChain Code node or the Edit Image node
- Check whether any connection uses the Slack signature secret
- Export the "Executions might fail" items as CSV and hand them out to owners
The Reverts section of the same notes lists two entries: removing the "Run once for each item" mode of the Execute Sub-workflow node, and removing the "Any workflow" caller policy. I read this to mean both removals were cancelled for this version. That is only my reading, so a team that uses either feature should read the release notes itself.
Around the time of v3.0.0, the earlier versions got fixes too.
- n8n@2.45.4 (2026-10-26) recreates removed n8n-sandbox sandboxes and reruns the workspace setup
- n8n@2.44.7 (2026-10-26) slows down how fast the Email Trigger (IMAP) node reconnects when the server drops its connection
- n8n@1.123.88 (2026-10-26) releases the SQLite write lock when the write connection fails to open, and updates certifi in the task runner to 2026.10.23
News we did not cover
- On GitHub trending (TypeScript), anomalyco/opencode gained 5,070 stars in the week
- Also on GitHub trending, AgriciDaniel/claude-seo gained 2,546 stars in the week
- OpenAI published a case on Uber bringing ChatGPT Work to all employees
Sources
- n8n, npm weekly downloads
- n8n releases: n8n@3.0.0, n8n@2.46.0, n8n@2.45.4, n8n@2.44.7, n8n@1.123.88