# 🎉 Node-RED 2.1.1 released

**URL:** <https://discourse.nodered.org/t/node-red-2-1-1-released/52554>\
**Category:** News\
**Created:** [22 October 2021 08:38 UTC](https://discourse.nodered.org/t/node-red-2-1-1-released/52554 "2021-10-22T08:38:45Z")\
**Posts on this page:** 1\
**Showing post:** 30

<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:** [25 October 2021 08:52 UTC](https://discourse.nodered.org/t/node-red-2-1-1-released/52554/30 "2021-10-25T08:52:48Z")

</div>

Thanks @jens_rossbach - I've just released 2.1.2 that should fix all of the issues raised here.

I tested it with both of your nodes and the others mentioned (although I never did find out which nodes @Hypnos was referring to).

If you still see any odd behaviours, please raise them as issues. As I've said, its important that we don't regress behaviour - even if we do update the best practices to follow.

> [@tada Node-RED 2.1.2 released](https://discourse.nodered.org/t/node-red-2-1-2-released/52691):
>
> Node-RED 2.1.2 is now available. This has resolved the outstanding issues with the TypedInput widget - but do let us know if you see anything odd.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-2-1-1-released/52554)._