n8n 1.46.0 → 1.47.0
1 version, 1 with breaking changes, 0 required stops
Version by version, oldest first
1.47.0 2024-06-20
Breaking
What changed?
Calling $(...).last() (or $(...).first() or $(...).all() respectively) without arguments is returning the the last item (or first or all items) of the output that connects the two nodes. Before it was returning the item/items of the first output of that node.
When is action necessary?
If you are using $(...).last() (or $(...).first() or $(...)all() respectively) without arguments for nodes that have multiple outputs (e.g. If, Switch, Compare Datasets, etc.) and you want it to default to the first output. In that case change it to $(...).last(0) (or first or all respectively).
This does not affect the Array functions [].last(), [].first().
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.