2 ms·
Usually when bringing in a library dependency, you don't use all features from the library. If the updates to some library relate to things you don't use, and t
by mvc 6y ago
Usually when bringing in a library dependency, you don't use all features from the library. If the updates to some library relate to things you don't use, and the rest remains compatible, then why update?
- mschuster91 6y agoBecause not every language / environment allows concurrent versions of a single library. PHP definitely does not, and for Java stuff IIRC you can only have one version of a library in one context of Tomcat/whatever application server you use. Therefore you want to keep your code at least somewhat up to date so that people don't run into weird bugs.
- scoopertrooper 6y agoSecurity teams generally have policies that require dependencies be up-to-date within a certain time frame. This is especially true if the dependency has a CVE somewhere within it - even if that CVE affects functionality that isn't utilised by the project.