self hosting
N8N Upgrade Guide
Update self-hosted n8n regularly, check release notes for breaking changes, and test important upgrades in a separate environment before touching production.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Update self-hosted n8n regularly, check release notes for breaking changes, and test important upgrades in a separate environment before touching production.
Key Facts
- Update cadence
- n8n recommends updating frequently, around at least monthly.
- Risk reduction
- Frequent updates avoid large version jumps.
- Pre-check
- Check release notes for breaking changes.
- Testing
- Use a test environment before updating production when possible.
Recommended Steps
- Back up the active database and n8n data directory.
- Read release notes between your current version and target version.
- Test the update in a separate environment.
- Update using the method that matches your installation, such as Docker or npm.
- Run critical workflows after the update and monitor logs.
Verification
- The instance starts on the target version.
- Critical workflows activate and execute.
- No breaking-change symptoms appear in logs or user workflows.
Warnings
- Skipping many versions at once increases upgrade risk.
- Do not update production without a rollback path and current backup.