n8n 0.67.0 → 0.68.0
4 versions, 1 with breaking changes, 0 required stops
Version by version, oldest first
0.67.1 – 0.67.3: no action items (3 versions)
0.68.0 2020-06-04
Breaking
What changed?
To make it easier to use the data which the Slack-Node outputs we no longer return the whole object the Slack-API returns if the only other property is "ok": true. In this case it returns now directly the data under "channel".
When is action necessary?
When you currently use the Slack-Node with Operations Channel -> Create and you use any of the data the node outputs.
How to upgrade:
All values that get referenced which were before under the property "channel" are now on the main level. This means that these expressions have to get adjusted.
Meaning if the expression used before was:
it has to get changed to:
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.