Hacker News new | ask | show | jobs
by gmueckl 666 days ago
It's easy to accidentally ship a minimum version requirement that is out of date when you also consistently use lock files pinned to newer versions. The code may silently depend on something introduced in a newer version pulled in by the lock file.
2 comments

You can have a CI builder using direct-minimal-versions to check this.
Point releases are often bugfix releases, i.e. not api changes but runtime changes. CI won’t help without very specific accompanying tests.
I have literally never run into this being a problem in practice. If someone downstream ever did notice, they can just specify a higher minimum version constraint.
Just have CI build with the minimum and the maximum.