Node-RED 3.1.1 is now available.
This is mostly a maintenance release with a number of fixes for issues reported against 3.1.0.
Full details in the changelog. The docker images are rebuilding as I type - will be available shortly.
15 Likes
Finally, after some time. Thanks...
Great, thanks.
Thanks Nick and the team 
I am seeing a number of nodes indicating a config error after the upgrade from 3.1.0, which is cleared by opening the node and closing it again. In particular for JSON nodes, if I export a node while it is showing the error then I see
[
{
"id": "442220a6.87889",
"type": "json",
"z": "c6d29a39.8cded",
"name": "",
"x": 347,
"y": 386,
"wires": [
[
"4e6acaf1.dd68fc"
]
]
}
]
On one of the nodes that has been opened and closed I see
[
{
"id": "d2192921.3b1a58",
"type": "json",
"z": "c6d29a39.8cded",
"name": "",
"property": "payload",
"action": "",
"pretty": false,
"x": 391,
"y": 113,
"wires": [
[
"805553da.d481c8",
"71035c91.4658d4"
]
]
}
]
So I guess that 3.1.1 does not cope with the missing properties.
I also see a similar thing on filter (rbe) nodes, where
[
{
"id": "e4d9fae4.b7c7a8",
"type": "rbe",
"z": "9d3f7d2b.521328",
"name": "",
"func": "rbe",
"gap": "",
"start": "",
"inout": "out",
"property": "payload",
"x": 100,
"y": 350,
"wires": [
[
"d9114c18.ab36d"
]
]
}
]
goes to
[
{
"id": "e4d9fae4.b7c7a8",
"type": "rbe",
"z": "9d3f7d2b.521328",
"name": "",
"func": "rbe",
"gap": "",
"start": "",
"inout": "out",
"septopics": true,
"property": "payload",
"topi": "topic",
"x": 100,
"y": 350,
"wires": [
[
"d9114c18.ab36d"
]
]
}
]
and a Range node where "property": "payload", is added.
Ah yes. We added improved validation of lots of node fields which were otherwise going ignored. I didn't take into account cases where older nodes don't have a particular properly set. Will revisit.
This is why I wanted to add the type validator (typeField), so that the user updates his node and repair the changed property
The update I pulled from nodered/node-red:latest still shows 3.1.0 both in the log at startup and in the Editor side panel. Not only has NR been restarted, but the host has been rebooted as well. And the browser cache has been cleared.
Seems this happened to me a year or so ago too but I can't recall if the issue was the Docker image or something I did wrong/missed.
Is there likely to be a re-release within a week or so, or should I bite the bullet and open and close the 20 or so nodes that are complaining?
Will there be another maintenance release with correct validation of the nodes? Currently I am waiting and will not upgrade my production system.
Yes, will revisit this week.
1 Like
Excellent, thanks.
I'm the only one???
Where?
Have you performed an upgrade?
Hi @LosinIt
I've just pulled nodered/node-red:latest from docker and can confirm it is 3.1.1.
If you run docker inspect nodered/node-red you'll get a big blob of JSON. At the start is an Id field that will begin "sha256:...." - can you share that as well as the RepoDigests entry?
Hi all,
I think I find an issue:
If you have a nested group inside of a subflow like in the picture, after you make the update to 3.1.1 the start-up will stuck in "Starting flows"
I'll do a 3.1.2 this afternoon.
3 Likes
Thank you very much for that!
