n8n 2.0 Just Dropped. Here's What You Need to Know Before You Touch That Update Button.
In8n 2.0 Just Dropped. Here's What You Need to Know Before You Touch That Update Button.
If you're running n8n workflows (or planning to), pause before upgrading.
n8n 2.0 landed back in December with breaking changes, and the team has been pushing bug-fix releases almost every other day through March. That's not a bad sign. It means they're actively fixing things. But it also means your workflows could behave differently after the upgrade.
What's been getting patched in March alone:
- Task runner stability (the sandboxed environment Code nodes now run in was hanging on connection failures)
- Form Node rendering and security (custom CSS sanitization tightened up)
- Kubernetes import issues and arm64 compatibility fixes
- Credential modal and collaboration fixes
They've shipped five patch releases in the first two weeks of March. The platform is stabilizing, but it's still moving fast.
What to do:
1. Check your current version. If you're on 1.x and things are working, there's no rush. 1.x gets security patches for 3 more months.
2. If you're already on 2.x, make sure you're on the latest patch (2.11.4 as of March 13)
4. Back up your workflows first. Export them. Every time. Non-negotiable.
The short version: n8n 2.0 is a real upgrade with real improvements. But "real upgrade" also means "real changes that can break things." Don't upgrade blind.
TLDR: n8n 2.0 broke ground in December. Three months later, the team is still patching (five releases in two weeks through March). Biggest recent fixes: task runner stability, Form Node security, and Kubernetes import handling. If you're on 1.x, you have 3 months of security support left. If you're on 2.x, update to 2.11.4. Either way, read the breaking changes doc and back up your workflows before touching anything.
If you've already upgraded and something broke, drop a comment. Happy to help you troubleshoot.