Why I recommend Renovate over any other dependency update tools
1–10 of 76 posts
Re: Why I recommend Renovate over any other dependency update tools
#2Re: Why I recommend Renovate over any other dependency update tools
#3Re: Why I recommend Renovate over any other dependency update tools
#4Every Monday I update dependencies. Review breaking changes, get to know what CVEs are out there, glance over changelogs
It takes less than an hour a week. It keeps me up to date on our dependencies
Re: Why I recommend Renovate over any other dependency update tools
#5Anyhow, this is useful to rollout dependabot.yaml config at scale: https://github.com/github/evergreen
Re: Why I recommend Renovate over any other dependency update tools
#6So, I picked up a pretty easy process I've used for the last 10 years (at decade old small company with plenty of legacy code, Microsoft, & now a startup using go/rust/js) Every Monday I update dependencies. Review breaking changes, get to know what CVEs are out there, glance over changelogs It takes less than an hour a week. It keeps me up to date on our dependencies
Re: Why I recommend Renovate over any other dependency update tools
#7There’s also the security aspect of supply chain attacks of “button press” updates.
I think having reports sent to repo owners that they can review with the team on a periodic basis instead of click-through maintenance might be a better model but I also understand the desire for mindless automation of what seems like a chore.
Re: Why I recommend Renovate over any other dependency update tools
#8So, I picked up a pretty easy process I've used for the last 10 years (at decade old small company with plenty of legacy code, Microsoft, & now a startup using go/rust/js) Every Monday I update dependencies. Review breaking changes, get to know what CVEs are out there, glance over changelogs It takes less than an hour a week. It keeps me up to date on our dependencies
Across how many repos? My team owns a dozen.
Re: Why I recommend Renovate over any other dependency update tools
#9So, I picked up a pretty easy process I've used for the last 10 years (at decade old small company with plenty of legacy code, Microsoft, & now a startup using go/rust/js) Every Monday I update dependencies. Review breaking changes, get to know what CVEs are out there, glance over changelogs It takes less than an hour a week. It keeps me up to date on our dependencies
Across how many repos? My team owns a dozen.
Ideally if there's multiple repos maintenance can be divided amongst those repo's owners, & once you've divided work between multiple people it becomes more valuable to have a tool help maintain process. These tools need buy in, I've found sometimes they'll go ignored & then the list of PRs becomes mixed up with random dependency PRs
Re: Why I recommend Renovate over any other dependency update tools
#10“AI, update this file from API V1 to API V2”