# Is multiple node versions usage necessary?

**URL:** <https://discourse.nodered.org/t/is-multiple-node-versions-usage-necessary/100357>\
**Category:** General\
**Created:** [11 February 2026 01:42 UTC](https://discourse.nodered.org/t/is-multiple-node-versions-usage-necessary/100357 "2026-02-11T01:42:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![aitor](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/aitor/32/97363_2.png) [@aitor](https://discourse.nodered.org/u/aitor)\
**Post date:** [11 February 2026 08:30 UTC](https://discourse.nodered.org/t/is-multiple-node-versions-usage-necessary/100357/2 "2026-02-11T08:30:35Z")

</div>

Hi Allan,

I ran into a similar situation—not because I needed multiple versions of the same node, but because I had to downgrade a node after an update broke something that worked fine in the previous version.

I opened a thread to ask for input, but it seems that managing or selecting specific node versions isn’t very straightforward at the moment.

> [@Node version selection in palette](https://discourse.nodered.org/t/node-version-selection-in-palette/89183):
>
> Hello everyone, I've been working on some Node-RED projects recently and needed to install a bunch of nodes from the palette. There’s a great selection, but some nodes are better maintained than others. Because of this, upgrading to the latest version sometimes messes up or changes my flows significantly. This got me wondering: why isn't there an option to pick a specific version of a node? In industrial automation, it's pretty standard to choose the software version you want, of course assumi…

---

_[View the full topic](https://discourse.nodered.org/t/is-multiple-node-versions-usage-necessary/100357)._