Сommunity node version is not updating

Describe the problem/error/question

The error does not allow me to update the community node version on the update button.

I expect that after clicking on the update button and update package. The latest version of node will be installed. But it doesn’t happen.

I have created and maintain n8n-nodes-kommo.
After making changes to the npm package, I execute:

  1. npm patch
  2. npm publish

The updated version of node is successfully published to npm.
Next, I go to n8n under community nodes https://mydomain.com/settings/community-nodes and see the “Update” button.
Next I click Update and update package.
Visually the update is successful. However, after refreshing the page, I see that the node version is still the same.
Rebooting the n8n container does not change the situation.
Only reinstalling the node helps.
Can you tell me what I am doing wrong?

What is the error message (if any)?

No error messages appear.
But the node is not updated after pressing the update button.

I recorded a short video to clearly demonstrate the error https://youtu.be/8tKinHtQzY0

Information on your n8n setup

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

I had the same issue. No idea what is causing it but i got it to work

The way I fixed:

  1. turned off workflows using the node
  2. uninstalled package
  3. restarted n8n instance
  4. reinstalled node

There are no issues with any existing workflows using the community node after that process so I didn’t dig any deeper.

That has become just what I do every time i need to update because as well as your issue I also ran into an issue where i updated and everything seemed successful, even after refreshing, but when I added a new node it was still from the old version.

1 Like

@Jon any idea what this could be?

No idea but I did create PAY-1424 as the internal dev ticket to look into this. I suspect the issue will be down to how we load the nodes.

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