n8n 2.0 Brings Breaking Security Changes That Could Disrupt Existing Workflows
n8n 2.0 is a significant upgrade that changes core defaults around Code nodes, task runners, Python execution, database handling, OAuth, and workflow publishing. Task runners are now enabled by default, and Code nodes can no longer access environment variables or use the $evaluateExpression() function as they previously could, which may silently break existing workflows. Python execution has also been overhauled, replacing the Pyodide-based model with an external task-runner approach that drops support for some previously available built-in variables. These changes are primarily security-driven, meaning workflows that ran without issue on n8n 1.x may behave differently after upgrading even without any manual edits. Developers are advised to test Code nodes with the new task-runner flag enabled and migrate secrets from environment variables to n8n credentials before attempting the upgrade.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in