Daily chron:
- Branch the repo, auto-update one dependency (ideally a smarter way to batch up groups)
- Run CI
- Auto-merge commit if CI passes, else discard commit.
- Loop to create a new branch for the next dependency waiting to be auto-updated.
Otherwise, not having the right testing or CI is technical debt like the grand parent commenter suggests.
On most of my projects I update dependencies whenever I can. On my older projects, I don't even touch any source code until after I update dependencies whenever I do maintenance on them. Typically either nothing breaks, I need to do some minor fixes, or I need to temporarily roll back some dependency to plan some bigger change. The thing is, if a new version is going to require any kind of non trivial work, I want to know about this as early as possible; especially if it is a lot of work. If you wait a year, you are looking at a lot of unknown work, which is basically technical debt you did not even know you had. I don't like that kind of uncertainty.
Mostly staying on top of things minimizes the work you actually have to do. And you get to benefit from all the fixes early. A lot of projects I join are hopelessly outdated. It's usually the first thing I fix. It's rare to find documented reasons why a particular thing can't or shouldn't be updated. If it's not documented, I'm just going to go ahead and fix it. In case it doesn't work, I'll document it.
How much of the team is awake, sober, and on the grid at that moment? Some times are worse than others for an outage.
That's also why agile processes work. Simply shortening feedback loops reduces the amount of work related to integrating and testing. Nothing magical about it. CI/CD works great too. Deploy when tested automatically instead of when the calendar says it is time to release. Get your feedback in early instead of weeks after a change.
A good way to fix a poorly performing team is simply to shorten their sprints. People hate this (because of all the meetings) but it makes sprints easier. Of course getting rid of sprints entirely is optimal. I actually prefer Kanban style processes usually and tend to separate planning iterations from day to day development work or releasing stuff. Leads to much more relaxed teams and it's also a lot easier on remote teams.
If course the above assumes you actually do the 5 times the testing before release. Most companies skipped that, and it showed.
Many companies have the wrong reflex of releasing less often when things don't go smoothly so they can test more not realizing that if they release more often, they can get away with less testing because there is less new stuff that can break.
Merging a full week of Chromium changes in all at once was just too many merge conflicts to deal with.
So I'd simulate as if I'd been merging daily by just doing 5-7 separate merges, which worked out well enough.