# 🎉 Node-RED 1.0.5 released

**URL:** <https://discourse.nodered.org/t/node-red-1-0-5-released/24522>\
**Category:** News\
**Created:** [9 April 2020 13:35 UTC](https://discourse.nodered.org/t/node-red-1-0-5-released/24522 "2020-04-09T13:35:09Z")\
**Posts on this page:** 5\
**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:** [9 April 2020 13:35 UTC](https://discourse.nodered.org/t/node-red-1-0-5-released/24522/1 "2020-04-09T13:35:09Z")

</div>

Node-RED 1.0.5 has been released with the usual small collection of fixes across the board.

Full details here: [https://github.com/node-red/node-red/releases/tag/1.0.5](https://github.com/node-red/node-red/releases/tag/1.0.5)

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [9 April 2020 19:01 UTC](https://discourse.nodered.org/t/node-red-1-0-5-released/24522/2 "2020-04-09T19:01:16Z")

</div>

Hi Nick (@knolleary) ,

Thanks for this new release!  
It seems there is - in particular cases - an issue with the pimped TypedInput fields.  
In our ui-svg node we [create](https://github.com/bartbutenaers/node-red-contrib-ui-svg/blob/panzoom/svg_graphics.html#L912) a table with typedinputs, but _ **some labels appear below the TypedInput fields** _ (but it is solved as soon as we make the config screen a bit wider):

![typedinput_bug](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/c/2c73921298b8b0f2b3fb293c59b3156aaee3aded.gif)

There isn't anything weird in the console log.  
If you need other information, please let me know!

Thanks!  
Bart

---

<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:** [9 April 2020 19:29 UTC](https://discourse.nodered.org/t/node-red-1-0-5-released/24522/3 "2020-04-09T19:29:15Z")

</div>

Thanks Bart.

I've pushed a fix for 1.0.6 which we can do early next week (pending any other issues that crop up)

Nick

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [10 April 2020 06:30 UTC](https://discourse.nodered.org/t/node-red-1-0-5-released/24522/4 "2020-04-10T06:30:05Z")

</div>

I have similar case but for custom type definitions where label is string

```auto
 var typedefinitions = {
                min: {
                    value: "min",
                    label: "Min ",
                    validate: RED.validators.number()
                },
                max: {
                    value: "max",
                    label: "Max ",
                    validate: RED.validators.number()
                },
                sec: {
                    value: "sec",
                    label: "Sec ",
                    validate: RED.validators.number()
                },
            }

```

And outcome is cropped currently

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/0/00b98885085723b1d6861dd0d18a55db6a32dc1a.png)

If already covered by fix, please ignore.

---

<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:** [9 June 2020 06:30 UTC](https://discourse.nodered.org/t/node-red-1-0-5-released/24522/5 "2020-06-09T06:30:08Z")

</div>

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