I read on this forum the minor version updates (2.1 → 2.2) don’t have an impact on the workflow.
What about the major version updates ?
Also, do you know if there is a way to automate the node version update in a workflow ?
If not, is it planned in the N8N roadmap or the only way is to do it manually ?
Same for me. I just discovered that if node has version 2.1 and I am trying to find out what are the diference from previous version but nothing… I like N8N but documentation is not as good and has to many issues when build complex workflows. I am wondering or evaluating if MAKE is better choice. I know that I have to pay for it, but I waste too much time for solving basics issues in n8n and that has a high cost… I
Hi @Adrien_Bruchon and @Adan_Palma
we don’t have an advanced management of node versions but hearing these needs from the community is useful to direct the evolution of n8n.
At the moment the document I refer to to check updates of nodes is the changelog on GitHub: Releases · n8n-io/n8n · GitHub
Thanks for your reply. The n8n comunity team is exceptional, please I dont misunderstand my words. I can not demand anything.
If i can, allow me suggest:
Include icon of node in the documentation of N8N, because some times i go to doc, I read but I am not sure if i am reading the doc for the node i am interesting in and I had to go worflow y check de node visually.
Move version text of node beside icon of node (could be)…
If posible explain a little better what improve in the new version of the node…