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.
The Configuration Nodes sidebar now shows if any of the nodes have configuration errors
Highlight errors in config node sidebar by knolleary · Pull Request #4529 · node-red/node-red · GitHub
The Import Nodes dialog for handling conflicts now does a better job of showing what nodes conflict
Improve feedback in import dialog to show conflicted nodes by knolleary · Pull Request #4550 · node-red/node-red · GitHub
The full changelog is available here: node-red/CHANGELOG.md at 1f412f3d78f06d469cb4495eb5c3b0d7e6c3f07b · node-red/node-red · GitHub
12 Likes
Thanks to the Node-Red team for this release
duaw
7 February 2024 06:54
3
The pi-release is here! Thanks!
Thanks for the updates.
node-red:dev ← node-red:tcp-request-node-reset-when-in-stay-connected-mode
opened 12:34PM - 01 Nov 23 UTC
<!--
## 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
As it was merged into the dev branch, it will be in the next major version (node-red v4).
system
7 April 2024 08:42
6
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
