Updated N8N but no new Merge node

[Wayne]

Hey, I’ve just updated my instance of n8n to 1.49.0 but I’m not getting the new Merge node, any idea why? Merge node shows version 2.1 (Latest)?

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[mariana-na]

Hi @Wayne ,

That is odd. Are you on cloud?
Could you try restarting your instance and see if it remains the same?

[Wayne]

@mariana-na, Self-hosted, I’ve restarted but no update.

I’ve tried on 2 instances, same results on both. Both are on different servers with different configs.

[barn4k]

Hm… I see the same on my cloud instance

But on my internal instance there is a new version…

Maybe there is something with the v1.50.1?

[mariana-na]

I updated a cloud instance to 1.49.0 this morning and the node is working as expected

But to test this I just updated an npm instance to 1.49.0 and the merge nodes I had already in workflows are on version 2.1

Only newly added nodes are updated

This is expected behaviour
Are you guys checking on nodes that were already in use or in newly added ones?

[Wayne]

@mariana-na new nodes

[mariana-na]

Thanks for confirming that.

Is this only happening with the merge node, or with any others too?

Could you share more details about your set ups, that could help understand where this comes from:

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[barn4k]

@mariana-na

Are you guys checking on nodes that were already in use or in newly added ones?

Nope, I added new Merge node, and the cloud instance (1.50.1) is showing that the latest Merge Node is v2.1, but my docker instance is on v1.49 and shows the correct v3

[Wayne]

@mariana-na Ok I have everything running in docker, all using postgres databases. I have 2 instances on 1.49 with this issue. One is running on a WSL2 system on an Ubuntu 24.04 LTS Distro on my home server, the other is running on Railway.app. The execution process hasn’t been changed so I assume default.

I also have another instance on a client’s Azure infrastructure on Ubuntu 24.04, they are on v1.49 also, running in Docker, and oddly, their merge nodes are v3.

Very odd.

[netroy]

I think think could be an issue of the browser cache not being revalidated. Next release should improve the cache headers. until then can you please try to hard refresh the frontend

[barn4k]

Yep, seems like so

[ria]

hi guys, release just went out with 1.51.0

fix(core): Ensure correct `Cache-Control` header on `/` as well (no-changelog)

fix(core): Use Custom cache-control headers force cache-revalidation on `/types/*.json` (no-changelog)