# 🎉 Node-RED 5 now available

**URL:** https://discourse.nodered.org/t/node-red-5-now-available/101239
**Category:** News
**Created:** [9 June 2026 09:29 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239 "2026-06-09T09:29:10Z")
**Posts on this page:** 1
**Showing post:** 41

<div class="post-metadata">

### Author: ![PizzaProgram](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizzaprogram/32/19431_2.png) [@PizzaProgram](https://discourse.nodered.org/u/PizzaProgram)
#### Post date: [13 June 2026 06:06 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/41 "2026-06-13T06:06:59Z")

</div>

> [@Vote for change. Debug "payload" only || or || the whole \`msg\`?](https://discourse.nodered.org/t/vote-for-change-debug-payload-only-or-the-whole-msg/101216/13):
>
> No. Node-RED 5 will refuse to run on anything prior to 22. There are simply too many security issues with old versions of dependencies that we had to move up the baseline.

In that case the editor should **not** notify users running prior Node.js v22 that :  
v5.0.0 is available.  
_(I've just got a popup like that after pressed Ctrl + F5 in my FFox.)_

Or at least it should not allow to try auto-update if it will fail anyway on pre v22 / Win7 .  
Is there any auto-failsafe test for that?

---

_[View the full topic](https://discourse.nodered.org/t/node-red-5-now-available/101239)._