Automating Dependency Updates with Renovate

Automating Dependency Updates with Renovate

1 / 5
volgende
Slide 1: Slide
newEditorBiologieBasisschoolGroep 1

In deze les zitten 5 slides, met tekstslides.

time-iconLesduur is: 15 min
Dit is niet oké

Onderdelen in deze les

Automating Dependency Updates with Renovate

I will give a short update on the Renovate's current status.



So for people who don't know this tool, Renovate is a bot that we currently use for our /lessonup repo to automate the process of updating dependencies.

Why should I care about dependency management?

Security

Bug fixes
/improvements
/access new feature

Upgrade debt

before jumping to the current state of Renovate . I would like to start with why do we need a dependency management strategy.

The first thing is the security aspect. And it was also the reason how we started investigate tools like reenabling dependabot or using renovate.


So every time we lag behind on keeping a dependency up to date, we're extending the vulnerabiltiy window, the window where our system is vulnerable to any known vulnerabilities.


The second is bug fixes and new features. The people who develpp and maintiain the libraires will also keep fixing issues they find. They'll keep making improvements. So if we keep lagging behind, we're sort of missing out on all those fixes that could potentially solve issues that we're having in our own codebase.

The third one is the upgrade debt, imagine there's a deoendency like 10 major versions behind. What would have initially been a simple or managble update, suddently become very big migration we have to deal with.

Before Renovate

  • Often forgotten

  • Low priority

  • Many dependencies severa versions behind

The strategy

Start with few packages and rules

Expand and group together

Improve continuously

So after understanding why dependency management is important for us. We'll the with the strategy we

Dependecny update before renovate is more like the tasks are often forgotten or we chose not to do it because we were on a tight schedule.

Once we decide to evaluate those auto dep update tools either Renovate and dependabot. We're going to see what this can do for us.


We start with few packages and then limit the amount of libaries we allowed Renovate to update. We make it run every day to provide more insights on how can we improve the rules.



Once we were sort of fairly confident that we had some idea of the amount of the work, we expand the continous monitor it.


And then we did some some incremental steps to improve the configs. First improve the config and then improve the automation, and then improve the schedule.

Current status

👍

Schedule: daily → weekly

automerge

👎

group
patch/minor updates

still many PRs with major bumps need a lot of code changes and additional manual work

CVE updates

extend to /infrastructure

So

We've been tuning the config and workflow for a while now, and it's in a much stable state,

and this is the current status overview:

1. Schedule: daily → weekly.

We started with few packages and then limit the amount of libaries we allowed Renovate to update. We make it run every day to provide more insights on how can we improve the rules.


Recently we were sort of fairly confident that we had some idea of the amount of the work, what kind of groups can be marked as automerged candidates. So now we have changed it to the weekly basis.

2. Automerge label. PRs that are safe to merge automatically carry an automerge label. For now is only limited to github action update. But developer-only tool is the next candidate we think it can be marked as automerged.

3. CVE updates. Security updates are handled separately and don't wait for the weekly window, they come through as soon as they're reported.

4. patch/minor updates. Patch and minor bumps are grouped into a single PR instead of one per package

5. we're also rolling the renovate setup out to the infrastructure repo atm

6. Major updates however they will be created per package because it possbily require some additional code changes or manual testing. And this will possbily be seen as part of adhoc work in the future. And there're few incidents reported by Fran which causes some warning messesages. We will continue monitoring the incidents and improving the process.

Statistics

lessonup-renovate[bot] opened its first PR on 2026-07-17 (#10791, qs 6.14.2 SECURITY).
Since then: 117 PRs.

Merged: 81 PRs
Open: 24 PRs
Closed unmerged: 12 PRs


  • auto-merged: 9

  • dead dep: 8

  • needs code changes: 24

  • some needs additional manual test: -

And this is some statisticish data. About how many renovate PRs are created and merged since July.

I won't go through the detail but overall it does save us some time. And also provide a better depedency health for our system. We also gain some insight that there're quite some dead dependencies due to previous cleanup or migration work.