chore: fix Dependabot prefix #251
Conversation
mpro7
requested review from
BalduinLandolt,
seakayone and
siers
as code owners
mpro7
changed the title
| @@ -23,9 +23,9 @@ updates: | |||
| - package-ecosystem: "cargo" | |||
| directory: "/" | |||
| schedule: | |||
| interval: "weekly" | |||
There was a problem hiding this comment.
Your title says increasing the interval, you have done the opposite.
IMHO we should keep the current schedule, is there any reason to change it?
There was a problem hiding this comment.
Indeed I made the mistake in the title (corrected, thanks!).
We have talked about it with @BalduinLandolt last week. The current state of this service/app is kind of static/simple - no authentication, no user profile, no fragile data etc. Therefore IMO it does not make sense for more frequent dependency updates. Especially if the new version is most probably going to be released on demand only and looking back, it was even less frequent than once per month.
Once we see there is necessity for the interval increasement, it could be done.
On top of that it is impossible to customize grouped PR title created by Dependabot, which will make confusion in the release notes. Which IMO is fine, until one would need to find out in which release specific dependency was bumped. Probably not common case, but still something to keep in mind.
There was a problem hiding this comment.
Your "reasons" do not convince me. I think merging some small PR every other week is not a problem.
That way we have the latests updates once we release on demand much quicker, which I deem to be more important.
There was a problem hiding this comment.
It is simply because my "reasons" are REASONS when you try to use them.
mpro7
changed the title
mpro7
changed the title
No description provided.