Keep your dependencies up to date

Posted by Joep Weijers on December 3, 2025

It is very likely that your software has external dependencies like libraries or frameworks. We know our software does. While it is very convenient you don’t have to write all functionalities from scratch, there is some overhead related to external dependencies. Here is how we manage that overhead.

It is great that developers provide libraries and frameworks for consumption by the public. Usually the code is open source, and you may even contribute new features to your favorite library. Those new features get packed up in a new release of the library.

Why should you update your dependencies?

New features and bug fixes are great reasons for updating your external dependencies. An update however might involve more than just changing the version number in your dependency management system. Because functionality might have been changed, deprecated or even removed. This means that you may end up now with Deprecation warnings in your project or it may even fail to compile at all.

If the maintainers of a library or framework use Semantic Versioning, then breaking changes, like the removal of functionality, are released in a major version release. This means that major version updates are probably more involved than a minor of patch update. That might entice you to not do major version updates. And that is fine, as long as the major version you are currently on is still supported by the maintainers of the library.

Library maintainers prefer not to support several major versions

Maintaining a library is work. And if you support multiple versions of that library, the maintenance burden increases significantly. A new feature or bug fix has to be implemented, tested and released for each major version. That is why library maintainers typically try to nudge you on to the latest versions of their libraries. And some have a clear support and end-of-life strategy to also make it clear for all users of the library what to expect for support.

If you decide not to do a major version upgrade of a library, you are essentially stuck. Because that library will continue to innovate and release new major versions. And it is very rare that updating multiple major versions is easier than a single major version update. It is an accumilating technical debt.

External dependencies pose a risk for your own software

Being on an unsupported version of a library and not able to quickly update is a big risk for your own software as well. Because if a security vulnerability is found in that library, then you are not able to quickly resolve the issue by updating to a safe, fixed version of that library. This means that your product may also be vulnerable for a longer time. And the longer a vulnerability is present, the higher the chance it gets exploited.

That is why one of the TOPdesk Minimum Quality Requirements states that all dependencies must be kept up to date. Most teams in TOPdesk have a monthly task to update dependencies. With good test coverage and tool support like mvn versions:display-dependency-updates and Renovatebot most updates are partially automated and go smoothly, leaving time to focus on any major updates.

Don’t get caught out when there is a reason that you suddenly must update a library. Take the effort (and pain) of periodically updating your dependencies.

Joep Weijers

Joep is a Developer Experience Engineer at TOPdesk with a keen interest in delivering quality software continuously. He loves playing around with GitLab CI pipelines, Selenium, Docker, Kubernetes and keeps in touch with his inner developer by educating his colleagues on testable Java code.

More Posts - Website