chore: Update renovate schedule#2405
Conversation
kaylareopelle
requested review from
a team,
arielvalentin,
dazuma,
hannahramadan,
robbkidd,
simi,
thompson-tomo and
xuan-cao-swi
as code owners
There was a problem hiding this comment.
I don't see this change having a noticeable affect on the qty of pr's we get. In fact I can see it having the opposite effect where in which we can now be waiting months to get updates.
To decrease the qty what I would suggest rather than changing the frequency, we instead increase update Grouping. For instance have a minor ruby group rather than individual prs & do the same for ci updates. That will bring the qty down without introducing a potential bottle neck causing lengthy delays.
We could also merge digest into patch group to decrease further.
| matchDepNames: ["ruby"], | ||
| matchUpdateTypes: ["digest", "patch"], | ||
| schedule: ["before 6am every weekday"], | ||
| schedule: ["before 6am every 4 weeks on Monday"], |
There was a problem hiding this comment.
This doesn't match the description. With this we can be waiting 4 weeks to test the latest ruby.
| matchDepNames: ["!ruby"], | ||
| matchUpdateTypes: ["patch"], | ||
| schedule: ["before 6am every weekday"], | ||
| schedule: ["before 6am every 4 weeks on Monday"], |
There was a problem hiding this comment.
4 weeks is a long time to wait for patches.
| { | ||
| matchDepNames: ["actions/setup-node", "ruby/setup-ruby"], | ||
| schedule: ["before 6am every weekday"], | ||
| schedule: ["before 6am on Monday"], |
There was a problem hiding this comment.
This is every weekday so that we can always be testing the latest ruby.
5 participants
We don't have any hard dependencies on our libraries, so I would like to turn down the frequency of renovate pull requests.
Every four weeks on Monday:
Every two weeks on Monday:
Every Monday:
Every Tuesday: