That's the question. No it's not. Just experienced bad example of holding back the nodejs based home automation system partials updates until something and then another something. It is bad idea. Update all and always as soon as possible. That little not updated thing bites hard and you can't e…

How true. While corporate IT has to be cautious about regular updates for various reasons. This kind of development and runtime environment really does need regular feeding, watering and toenail clipping. :grinning: My home systems get updated ASAP at the OS and application layers. Actually my work…

I have eight systems running node-red, mostly Pis. Six of those are in 'production' situations doing a job which is not changing. If every time a new version was released for any one of the nodes I updated them all I would forever be updating and testing. For systems that are working without issu…

As long as you have a test system that you do keep updating, this probably doesn't matter. I think that what our Estonian friend is saying is that there are risks involved with not updating for a while in the very fast moving world of Node.js. You may end up with an unexpected breaking change and i…

Is there a question of unattended upgrades lurking in the background here? I'm old enough to belong to the "if it ain't broke, don't fix it" school. My home automation runs completely off the net and tends to fall several generations behind the latest releases. (One system is at NR version 0.19.4.)…

[image] drmibell: Is there a question of unattended upgrades lurking in the background here? Do you mean that the system might be being updated without your knowledge when you don't want it to, or are you asking about how to make it automatically update?

[image] drmibell: I don't think there is any way those installations can break unless I cause it. Well, that is the issue really. When you do need to update, you will be updating so much that any new errors will be impossible to track down. Was it a breaking change in NR, in some deep depende…

While I've had a few issues with serial port related and sqlite and recompilations, this is very much the exception for minor updates. Only really becomes an issue when taking on a new major version of Node.js. Hence my previous comments.

[image] TotallyInformation: When you do need to update, you will be updating so much that any new errors will be impossible to track down. True, but not really relevant to my way of working. I always have a fully updated and functional system that is deployable but not deployed. Changes to it…

To update or not to update

General

drmibell 21 March 2020 18:09 9

Yes and no. As mentioned in an earlier discussion, there seems to be growing interest here in automating minor OS and software upgrades. The user asks for them and knows when they happen. On the other hand, even if an upgrade is not technically "breaking" (major), it could create incompatibilities or require re-compilation of some nodes or libraries. Package managers are smart but not infallible.

Topic		Replies	Views
Using snap to update nodejs General	9	192	6 October 2023
How to update Node-RED? General	6	3482	27 February 2020
Lost everything after Update General	7	563	24 January 2022
Where is Node-RED 1.0? News	27	3822	7 September 2019
Installation/upgrade node question General	2	129	29 May 2023

To update or not to update

Related topics