n8n 0.117.0 → 0.118.0
1 version, 1 with breaking changes, 0 required stops
Version by version, oldest first
0.118.0 2021-05-02
Breaking
What changed?
The minimum Node.js version required for n8n is now v14.
When is action necessary?
If you're using n8n via npm or PM2 or if you're contributing to n8n.
How to upgrade:
Update the Node.js version to v14 or above.
What changed?
In the Postgres, CrateDB, QuestDB and TimescaleDB nodes the Execute Query operation returns the result from all queries executed instead of just one of the results.
When is action necessary?
If you use any of the above mentioned nodes with the Execute Query operation and the result is relevant to you, you are encouraged to revisit your logic. The node output may now contain more information than before. This change was made so that the behavior is more consistent across n8n where input with multiple rows should yield results acccording all input data instead of only one. Please note: n8n was already running multiple queries based on input. Only the output was changed.
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.