Extract Dependency Data on Scale with Renovate
summary
Renovate is used to extract dependency data across repositories by running managers (100+ supported) and emitting concise JSON reports or pushing them to S3; it supports 65 data sources, custom managers and presets and dry‑run modes for extract/lookup so teams get both discovered items and available updates. A Backstage plugin runs Renovate at scale with horizontal nodes and produced examples like 3,834 dependencies and 433 updates for Backstage, and N26 reports 44,000 tracked items (~400,000 historical records).
AI-written summary · about
chapters (13)
- 0:00Renovate and dependency challenges
- 1:03Why dependency data matters at scale
- 7:14What Renovate is and how it works
- 10:48Custom managers and internal deps
- 14:40Three ways to extract dependency data
- 18:11Renovate reports for large-scale analysis
- 25:02Tools built on Renovate for insights
- 29:06Live demo with Backstage
- 35:14N26 use case with 400k datasets
- 37:49Limitations and future of extraction
- 41:04Configuring Renovate workflow
- 45:31Caching strategies and registry efficiency
- 46:13Q&A
related talks
31mRenovate/Dependabot: How to Take Back Control of Dependency Updates
45mHow to Automate Dependency Updates with the Renovate@Roche Bot
25mRenovate, or how to keep your project up to date!
45mHow to Automate Dependency Updates with the Renovate@Roche Bot
33mAutomated update management with
05mQuantifying your reliance on Open Source software
42mDependency Updates: Before and After
16mRenovate to the Rescue
