n8n 1.101.0 → 1.102.0
2 versions, 1 with breaking changes, 0 required stops
Version by version, oldest first
1.101.1: no action items (1 version)
1.101.2 – 1.101.3: released after 1.102.0; not on this route
1.102.0 2025-07-07
Breaking
What changed?
The N8N_RUNNERS_ALLOW_PROTOTYPE_MUTATION flag has been replaced with N8N_RUNNERS_INSECURE_MODE. The new flag disables all task runner security measures and is intended as an escape hatch for users who value compatibility with libraries like puppeteer at the cost of security.
When is action necessary?
If you are using the N8N_RUNNERS_ALLOW_PROTOTYPE_MUTATION flag, or if you find that the task runner does not currently support an external module that you rely on, then consider setting N8N_RUNNERS_INSECURE_MODE=true, at your own risk.
From github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md
Release notes from github.com/n8n-io/n8n/releases, and packages/cli/BREAKING-CHANGES.md, and CHANGELOG.md, checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. n8n keeps its breaking changes in packages/cli/BREAKING-CHANGES.md, one section per version (“What changed?”, “When is action necessary?”); each section is quoted whole as “Breaking” on its version. The “BREAKING CHANGES” sections of CHANGELOG.md (0.198.0, 1.0.0, 1.27.0) are quoted too, and each section of the docs page “n8n 2.0 breaking changes” is quoted as “Upgrade guide” on 2.0.0. GitHub release notes are commit lists and are not quoted. Versions come from npm (package n8n). No required stop is recorded: neither file nor the 2.0 page names a version to install first.