n8n 1.102.0 → 1.103.0
4 versions, 1 with breaking changes, 0 required stops
Version by version, oldest first
1.102.1 – 1.102.3: no action items (3 versions)
1.102.4: released after 1.103.0; not on this route
1.103.0 2025-07-14
Breaking
What changed?
We will no longer be allowing users to use responseData within the Webhook node since this is now sandboxed in an iframe, which may break workflows relying on browser APIs like localStorage and fetch from within custom code.
When is action necessary?
If your workflow is using the Webhook node and uses JavaScript in responseData to make fetch calls or access localStorage, you may need to refactor it due to the new iframe sandboxing.
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.