n8n 0.110.0 → 0.111.0
4 versions, 1 with breaking changes, 0 required stops
Version by version, oldest first
0.110.1 – 0.110.3: no action items (3 versions)
0.111.0 2021-03-12
Breaking
What changed?
In the Dropbox node, now all operations are performed relative to the user's root directory.
When is action necessary?
If you are using any resource/operation with OAuth2 authentication.
If you are using the folder:list operation with the parameter Folder Path empty (root path) and have a Team Space in your Dropbox account.
How to upgrade:
Open the Dropbox node, go to the OAuth2 credential you are using and reconnect it again.
Also, if you are using the folder:list operation, make sure your logic is taking into account the team folders in the response.
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.