Upgrade Path

n8n 1.23.0 → 1.24.0

1 version, 1 with breaking changes, 0 required stops

Version by version, oldest first

1.24.0 2024-01-10

Breaking

What changed?

The flag N8N_CACHE_ENABLED was removed. The cache is now always enabled.

Additionally, expressions in credentials now follow the paired item, so if you have multiple input items, n8n will try to pair the matching row to fill in the credential details.

In the Monday.com Node, due to API changes, the data structure of entries in column_values array has changed

When is action necessary?

If you are using the flag N8N_CACHE_ENABLED, remove it from your settings.

In regards to credentials, if you use expression in credentials, you might want to revisit them. Previously, n8n would stick to the first item only, but now it will try to match the proper paired item.

If you are using the Monday.com node and refering to column_values property, check in table below if you are using any of the affected properties of its entries.

ResourceOperationPreviousNew
BoardGetownerowners
BoardGet Allownerowners
Board ItemGettitlecolumn.title
Board ItemGet Alltitlecolumn.title
Board ItemGet By Column Valuetitlecolumn.title
Board ItemGetadditional_infocolumn.settings_str
Board ItemGet Alladditional_infocolumn.settings_str
Board ItemGet By Column Valueadditional_infocolumn.settings_str

*column.settings_str is not a complete equivalent additional_info

From github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md

Full release notes for 1.24.0

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.