The future of dependency management, seen from 2022
summary
Dependency upgrades are slow and error prone with Gradle defaults, version ranges break reproducibility, and bots like Dependabot/Renovate generate noisy PRs and waste CI. The demonstration uses refreshVersions (a Gradle plugin) which centralizes versions in a single versions.properties, queries available updates in parallel, shows inline candidates, lets you pick a safe increment, and avoids build-cache invalidation. Notes on Version catalogs, dependency locking, and tools like Dependency Guard clarify compatibility, transitive surprises, and where metadata and discovery tooling are missing.
AI-written summary · about
chapters (6)
- 0:00Introduction and speaker background
- 3:57Common dependency upgrade problems
- 11:22Refresh Versions plugin demo
- 21:53Risks of third-party dependencies
- 27:31Library discovery challenges
- 34:55Q&A and closing remarks
related talks
41mThe future of dependency management, seen from 2022
42mDependency Updates: Before and After
31mRenovate/Dependabot: How to Take Back Control of Dependency Updates
01h 01mDependency Management with Gradle 6.0
41mRenovate/Dependabot: How to Reclaim Control Over Dependency Updates
31mStrengthen Our Developer eXperience to Face Obsolescence and View...
24mManaging Dependencies with Confidence
36mNasty Dependencies: Surviving and fixing bugs in 3rd-party libra…