# 🎉 Node-RED 1.0 Released

**URL:** <https://discourse.nodered.org/t/node-red-1-0-released/16091>\
**Category:** News\
**Created:** [30 September 2019 13:19 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091 "2019-09-30T13:19:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [30 September 2019 13:19 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/1 "2019-09-30T13:19:06Z")

</div>

In our last update, I said we aimed to release Node-RED 1.0 in September.

Today is the last day of September.

Here is Node-RED 1.0: [https://nodered.org/blog/2019/09/30/version-1-0-released](https://nodered.org/blog/2019/09/30/version-1-0-released)

Enjoy.

---

<div class="post-metadata">

**Author:** ![kuema](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kuema/32/6542_2.png) [@kuema](https://discourse.nodered.org/u/kuema)\
**Post date:** [30 September 2019 13:25 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/2 "2019-09-30T13:25:15Z")

</div>

Precision landing on the release date. 😀

A big thank you to all contributors for all your hard work. 🍻

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [30 September 2019 13:27 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/3 "2019-09-30T13:27:05Z")

</div>

🍾🎂🎉🥇

BRAVO, Hipp, Hipp Hurrrray

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [30 September 2019 13:31 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/4 "2019-09-30T13:31:31Z")

</div>

And nice to see no outstanding warnings or vulnerabilities 🙂

---

<div class="post-metadata">

**Author:** ![Nxito](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nxito/32/88293_2.png) [@Nxito](https://discourse.nodered.org/u/Nxito)\
**Post date:** [30 September 2019 15:07 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/5 "2019-09-30T15:07:49Z")

</div>

Finally version 1.0.0! looks great.

I just found this by lookingthe nodes of this link https://flows-new.nodered.org/collection/590bc13ff3a5f005c7d2189bbb563976  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/c/ce8ba6c2c62b8ab7d87be55420f64944a882954b.png)  
I don't think it has to do with the new version, but it looks weird

---

<div class="post-metadata">

**Author:** ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)\
**Post date:** [30 September 2019 15:15 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/6 "2019-09-30T15:15:07Z")

</div>

Nick, the links in the blog post for the flows library still use the beta address, should that be changed at a later stage now that it went live on the regular library as well? I only noticed as the person responding above me had the link in it.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [30 September 2019 15:18 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/7 "2019-09-30T15:18:52Z")

</div>

I wondered how that url had leaked out.... mea culpa. Thanks for alerting me 😉

---

<div class="post-metadata">

**Author:** ![mtoko](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mtoko/32/138_2.png) [@mtoko](https://discourse.nodered.org/u/mtoko)\
**Post date:** [30 September 2019 15:36 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/8 "2019-09-30T15:36:19Z")

</div>

Thanks to everybody involved especially Nick! Great job !

---

<div class="post-metadata">

**Author:** ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)\
**Post date:** [30 September 2019 16:55 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/9 "2019-09-30T16:55:42Z")

</div>

> [@mtoko](#):
>
> Thanks to everybody involved especially Nick

And don’t forget about Dave either, especially on lucky Monday 😉

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [30 September 2019 17:25 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/10 "2019-09-30T17:25:08Z")

</div>

Silly question... how do I upgrade to Node-RED 1.0 ???

If I do... _sudo npm install -g --unsafe-perm node-red@next_ I get v1.0.0-beta 4

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [30 September 2019 17:26 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/11 "2019-09-30T17:26:19Z")

</div>

```auto
sudo npm install -g --unsafe-perm node-red

```

without the `@next` will get you 1.0.0.

But I'll update the next tag in a bit to point at 1.0.0

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [30 September 2019 17:26 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/12 "2019-09-30T17:26:46Z")

</div>

Thanks Nick

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [30 September 2019 19:16 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/13 "2019-09-30T19:16:03Z")

</div>

Actually, I just did `npm update` (`npm update -g` for a normal install). Seemed to work just fine

---

<div class="post-metadata">

**Author:** ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)\
**Post date:** [30 September 2019 21:13 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/14 "2019-09-30T21:13:07Z")

</div>

Or if you’re on a compatible device/installation, run the pi install script again.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [1 October 2019 06:03 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/15 "2019-10-01T06:03:34Z")

</div>

Subflow bug:

- hamburger menu \> subflows \> create subflow
- 1 input, 1 output, connect the 2.
- edit properties, appearance tab
- change the color
- new subflow node appears with new color, deploy
- add new flow
- drag the subflow node into the flow

Result: it changes color back to the original color (#DDAA99)  
It only does this once strangely enough.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [1 October 2019 06:25 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/16 "2019-10-01T06:25:26Z")

</div>

@bakman2 if you are sure you have a reproducible set of steps, please raise an issue.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [1 October 2019 06:33 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/17 "2019-10-01T06:33:57Z")

</div>

Thanks, [done](https://github.com/node-red/node-red/issues/2298).

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 October 2019 09:05 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/18 "2019-10-01T09:05:27Z")

</div>

Just upgraded one of my Pis using the bash script. It didn't ask whether it should install the extra pi nodes (I don't know whether it should) but on restart I get

```auto
1 Oct 09:54:18 - [info] Waiting for missing types to be registered:
1 Oct 09:54:18 - [info] - rpi-gpio out (provided by npm module node-red-node-pi-gpio)

```

There did not seem to be any errors in the install log.  
I installed the node via the palette and now all is well.

---

<div class="post-metadata">

**Author:** ![anITiot](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/anitiot/32/12697_2.png) [@anITiot](https://discourse.nodered.org/u/anITiot)\
**Post date:** [1 October 2019 09:55 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/19 "2019-10-01T09:55:11Z")

</div>

Update done  
Ubuntu 18.04 / 64bit on Raspberry PI 4

npm install -g --unsafe-perm node-red  
pm2 restart node-red

Now it's up to me learn and do more from my newbie point, my last mqtt test works.

---

<div class="post-metadata">

**Author:** ![tilleul](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tilleul/32/78_2.png) [@tilleul](https://discourse.nodered.org/u/tilleul)\
**Post date:** [1 October 2019 10:57 UTC](https://discourse.nodered.org/t/node-red-1-0-released/16091/20 "2019-10-01T10:57:35Z")

</div>

Congratulations on the release of NR 1.0 !  
I noticed that the show/hide switch to show/hide nodes labels has been replaced with a checkbox .. Unfortunately, although when checked it shows "show", when it's unchecked it shows "hide" which could be understood as **don't hide, so "show"** the text of the checkbox should not reflect the state IMHO.

[Next page](https://discourse.nodered.org/t/node-red-1-0-released/16091.md?page=2)