n8n 1.82.0 → 1.83.0
3 versions, 2 with breaking changes (1 repeats an earlier entry), 0 required stops
Version by version, oldest first
1.82.1 2025-03-04
Breaking
What changed?
The Form nodes no longer allows input field types for custom HTML to prevent malicious javascript from being added.
When is action necessary?
If you were previously using input in the custom HTML for a Form node.
From github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md
1.82.2: no action items (1 version)
1.82.3 – 1.82.4: released after 1.83.0; not on this route
1.83.0 2025-03-12
Breaking
Same text as in 1.82.1, above.
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.