3 ms·
I think it comes down to what kind of product you're building and what kind of libraries you're using. If you're doing some web-facing product that's being cont
by taneq 11y ago
I think it comes down to what kind of product you're building and what kind of libraries you're using. If you're doing some web-facing product that's being continually developed, and there's a security update in a library or framework, then sure.
If you're building a traditional piece of software (no "evergreen" continual updates, maybe even with no upgrade process at all eg. device firmware) then just using a library internally, and your requirements aren't changing, then continually updating it is busywork at best, and a risk to the reliability and stability of your project at worst.
It's not "technical debt" to skip point releases that don't add anything to your project, since you avoid potentially re-integrating changes to the same features if they change multiple times, and there's a good chance you'll never need to update at all.