n8n 1.1.0 → 1.2.0
2 versions, 1 with breaking changes, 0 required stops
Version by version, oldest first
1.1.1: no action items (1 version)
1.2.0 2023-08-09
Breaking
What changed?
For the Linear node, priority in issue creation is 4 (previously incorrectly 3) for Low.
When is action necessary?
If you were using Low, you were setting a priority of Normal, so please double check you are setting the priority you intend.
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.