n8n 0.231.0 → 0.232.0
2 versions, 1 with breaking changes, 0 required stops
Version by version, oldest first
0.231.1: no action items (1 version)
0.231.2 – 0.231.3: released after 0.232.0; not on this route
0.232.0 2023-06-07
Breaking
What changed?
Due to Node.js/OpenSSL upgrade, the following crypto algorithms are not supported anymore.
- RSA-MD4
- RSA-MDC2
- md4
- md4WithRSAEncryption
- mdc2
- mdc2WithRSA
When is action necessary?
If you're using any of the above mentioned crypto algorithms in Crypto node in any of your workflows, then please update the algorithm property in the node to one of the supported values.
What changed?
The LoneScale List node has been renamed to LoneScale.
When is action necessary?
If you have used the LoneScale List node in any of your workflows.
How to upgrade:
Update any workflows using LoneScale List to use the updated node.
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.