# 🎉 Node-RED 3.1.4 released

**URL:** <https://discourse.nodered.org/t/node-red-3-1-4-released/85263>\
**Category:** News\
**Created:** [6 February 2024 17:14 UTC](https://discourse.nodered.org/t/node-red-3-1-4-released/85263 "2024-02-06T17:14:30Z")\
**Posts on this page:** 6\
**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:** [6 February 2024 17:14 UTC](https://discourse.nodered.org/t/node-red-3-1-4-released/85263/1 "2024-02-06T17:14:30Z")

</div>

Node-RED 3.1.4 is now available.

This is mostly a maintenance release with lots of fixes for issues reported since our last release.

There are a couple enhancements thrown in for good measure - not something we typically do for maintenance releases, but these were suitably self-contained to include.

1. The Configuration Nodes sidebar now shows if any of the nodes have configuration errors

2. The Import Nodes dialog for handling conflicts now does a better job of showing what nodes conflict

The full changelog is available here: [node-red/CHANGELOG.md at 1f412f3d78f06d469cb4495eb5c3b0d7e6c3f07b · node-red/node-red · GitHub](https://github.com/node-red/node-red/blob/1f412f3d78f06d469cb4495eb5c3b0d7e6c3f07b/CHANGELOG.md#314-maintenance-release)

---

<div class="post-metadata">

**Author:** ![softy2k](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/softy2k/32/23707_2.png) [@softy2k](https://discourse.nodered.org/u/softy2k)\
**Post date:** [6 February 2024 17:40 UTC](https://discourse.nodered.org/t/node-red-3-1-4-released/85263/2 "2024-02-06T17:40:13Z")

</div>

Thanks to the Node-Red team for this release

---

<div class="post-metadata">

**Author:** ![duaw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/duaw/32/20970_2.png) [@duaw](https://discourse.nodered.org/u/duaw)\
**Post date:** [7 February 2024 06:54 UTC](https://discourse.nodered.org/t/node-red-3-1-4-released/85263/3 "2024-02-07T06:54:55Z")

</div>

The pi-release is here! Thanks!

---

<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:** [7 February 2024 08:07 UTC](https://discourse.nodered.org/t/node-red-3-1-4-released/85263/4 "2024-02-07T08:07:14Z")

</div>

Thanks for the updates.  
Although I don't see in the changelog, was this change merged as well ? Or better put - when is it expected to be merged ?

> <https://github.com/node-red/node-red/pull/4406>
>
> \<!--
> \## Before you hit that Submit button....
> 
> Please read our \[contribution …guidelines\](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
> before submitting a pull-request.
> 
> \## Types of changes
> 
> What types of changes does your code introduce?
> Put an \`x\` in the boxes that apply
> \--\>
> 
> \- \[\] Bugfix (non-breaking change which fixes an issue)
> \- \[X\] New feature (non-breaking change which adds functionality)
> 
> \<!--
> If you want to raise a pull-request with a new feature, or a refactoring
> of existing code, it \*\*may well get rejected\*\* if it hasn't been discussed on
> the \[forum\](https://discourse.nodered.org) or
> \[slack team\](https://nodered.org/slack) first.
> 
> \--\>
> 
> \## Proposed changes
> 
> This PR lets \`msg.reset = true; \` (boolean) reset the tcp-request node when it is set to remain connected. This allows the user to "kick" the connection if required so it forces a reconnect - or also allows them to send msg.host and/or msg.port to connect to a different server instead.
> 
> \## Checklist
> 
> 
> \- \[X\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
> \- \[X\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[X\] I have run \`npm run test\` to verify the unit tests pass
> \- \[\] I have added suitable unit tests to cover the new/changed functionality

---

<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:** [7 February 2024 08:41 UTC](https://discourse.nodered.org/t/node-red-3-1-4-released/85263/5 "2024-02-07T08:41:59Z")

</div>

As it was merged into the dev branch, it will be in the next major version (node-red v4).

---

<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:** [7 April 2024 08:42 UTC](https://discourse.nodered.org/t/node-red-3-1-4-released/85263/6 "2024-04-07T08:42:29Z")

</div>

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