Disabling Scheduled Dependency Updates(davidism.com)

18 pointsby benhoytvor 2 Jahren7 comments

https://davidism.com/disabling-scheduled-dependency-updates/

7 comments

This guy calls it out here, but I will say that the notifications page on github could do with a redesign. If you're in a busy org for your job, it's not easy to see everything in the org (they limit showing number of notifications per repo), and the volume of notifications from your job org will cover up anything in your personal/following repos.

Sure you could unfollow work repos you aren't interested in, but you're automatically following any new ones.

charrondevvor 2 Jahren

In my case I recently moved all my company org access to a separate GitHub account. It definitely solves this issue at least.

maximilianroosvor 2 Jahren

An alternative is to automatically merge dependency changes which pass the tests. Then there's no need for any intervention unless something needs your attention, just dismiss the notification.

We do this at PRQL, with: https://github.com/PRQL/prql/blob/12b1bb65afd5b67f34b98d0ac1...

norman784vor 2 Jahren

TBH with Rust it's easier, because if it compiles, it works. While in the dynamic languages ecosystems is more risky and will require either way manual review, unless you have 100% test coverage that I would assume is very rare.

cesnjavor 2 Jahren

You get to choose either the mind-numbing churn of constant updates, the risk of updates piling up and becoming unmanageable, or shipping software with vulnerabilities. None of these options sounds fun.

donatjvor 2 Jahren

I really wish there was a step before opening a PR, like a page with a list of what's out of date that let's you click a button to open a PR for one or more dependency updates.

cesnjavor 2 Jahren

Renovate has a feature called "Dependency Dashboard" which does exactly that.