Breaking Change in Code Node - Upgrade to 1.78.0

Questions
, , ,
1

Hi,

First off, I love n8n and really appreciate all the work that goes into it! That said, I wanted to report a breaking change I encountered after upgrading to version 1.78.0. In the Code node, the syntax $items('NodeName') stopped working and had to be updated to $('NodeName').all().

This change was not clearly communicated, and as a result, several of my production workflows suddenly stopped working, causing major disruptions. I’m not sure exactly which version introduced this, as I upgraded from around 1.65, but such a breaking change should follow proper semantic versioning. A major version bump (e.g., 2.0.0) would have been more appropriate to prevent unexpected failures.

Additionally, since there is no way to downgrade from the admin panel, recovering from this kind of issue is unnecessarily difficult. I’d really appreciate it if future updates followed stricter versioning and included clearer communication about breaking changes.

Thanks again for all the great work on n8n!

2

Thanks a lot for reporting this. Very sorry for this problem. We are already investigating what is going on there.

1 Like
3

Hey @Achille !

First of all my deepest apologies that you had to face this issue. When we implemented Task Runner, there was an oversight from our end and the support for $items(...) got accidentally dropped. Thank you for reporting this bug so we were able to fix it. It will be fixed when this PR is merged and released. We are fully committed to not make any breaking changes except in major version releases.

3 Likes
4

New version [email protected] got released which includes the GitHub PR 13368.

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.