# 🎉 Node-RED 1.2.5 released

**URL:** <https://discourse.nodered.org/t/node-red-1-2-5-released/36095>\
**Category:** News\
**Created:** [17 November 2020 21:32 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095 "2020-11-17T21:32:28Z")\
**Posts on this page:** 13\
**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:** [17 November 2020 21:32 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/1 "2020-11-17T21:32:28Z")

</div>

Node-RED 1.2.5 is now available.

A fix in 1.2.4 failed to handle an edge case that wasn't spotted in testing. Thankfully it was spotted very quickly and we've published the fix.

~~Node-RED 1.2.4 is now available.~~

Notable fixes include:

- New Russian locale support
- Fixes an issue where custom keyboard shortcuts were being overridden unexpectedly
- Support for displaying bigint types in the Debug sidebar
- Fixes a memory leak handling node status messages with subflows
- Large flows should load quicker in the editor due to other performance improvements around status handling.

> **[Release 1.2.4: Maintenance Release · node-red/node-red](https://github.com/node-red/node-red/releases/tag/1.2.4)**
>
> Editor
> 
> Support bigint types in Debug sidebar
> Clear retained status of deleted nodes
> Prevent needless retention of node status messages
> Update projects dialogs to use TypedInput-cred input
> Restore ...

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [17 November 2020 21:38 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/2 "2020-11-17T21:38:09Z")

</div>

> [@knolleary](#):
>
> Support for displaying bigint types in the Debug sidebar

Ah - very nice.

I see in the code you do `toString()` on the `bigint`.  
I am curious to know your thoughts on whether the string representation (in the debug output) should include an `n` (e.g. `123456789n`) to signify it was a bigint?

---

<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:** [17 November 2020 21:45 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/3 "2020-11-17T21:45:27Z")

</div>

I decided to go with the pragmatic solution to get something working. Given the lack of support for BigInt in JSON, I decided to go with String to preserve the value if the user copy/pastes it.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [17 November 2020 22:40 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/4 "2020-11-17T22:40:06Z")

</div>

I'm getting an error after updating;

![ezreplace](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/8/3802bc6f91e097a4a06573463f4c8686540829dd.jpeg)

I'm not seeing anything in the node-RED log, or the browser console.

But by starting in safe mode, I've narrowed it down to the `rbe` node - Just add the `rbe` node to the editor, deploy, and refresh F5.

Node-RED version: v1.2.4  
Node.js version: v12.19.1  
Linux 4.14

---

<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:** [17 November 2020 22:42 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/5 "2020-11-17T22:42:34Z")

</div>

Odd - can't reproduce that here. Can you send me you flows file directly?

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [17 November 2020 22:52 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/6 "2020-11-17T22:52:08Z")

</div>

It's not a flow, it seems to be just adding the rbe node to the workspace.  
Here, I add the rbe node, deploy, and then F5 refresh.

 ![error](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/f/fffdc7652fb30f00fea194f6d482cd3f702237d1.gif)

---

<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:** [17 November 2020 22:52 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/7 "2020-11-17T22:52:59Z")

</div>

Right - but I can't reproduce that. If you sent me your flows file I'd be able to see what is going on when is being loaded.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [17 November 2020 23:00 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/8 "2020-11-17T23:00:49Z")

</div>

OK, just PM'd 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:** [17 November 2020 23:13 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/9 "2020-11-17T23:13:52Z")

</div>

Node-RED 1.2.5 published with the fix. Sorry for that.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [17 November 2020 23:22 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/10 "2020-11-17T23:22:43Z")

</div>

All good now 👍  
Thanks for the quick fix.

---

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [18 November 2020 17:03 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/11 "2020-11-18T17:03:20Z")

</div>

@knolleary

I see the Github link still points to 1.2.4

Colin J

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [18 November 2020 19:33 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/12 "2020-11-18T19:33:44Z")

</div>

> [@mudwalker](#):
>
> I see the Github link still points to 1.2.4

Probably because v1.2.4 is the actual update, and the link shows users what changes have been made by that update.  
(Whilst v1.2.5 just fixes an edge case in v1.2.4)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [17 January 2021 19:34 UTC](https://discourse.nodered.org/t/node-red-1-2-5-released/36095/13 "2021-01-17T19:34:03Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.