Frank Thomas
Frank Thomas
This has been superseded by https://github.com/alonsodomin/cron4s/pull/404 and can be closed.
I don't use the Scala Steward Docker image and I'm also not very familiar with the Docker ecosystem. I'll probably merge anything Docker related if it sounds reasonable to me....
The approach look good to me or at least I don't have a better idea how to use published rules with the Scalafix CLI. But I don't think that the...
> A solution that could work in this case is to add a new `toolClasspathCommand` We could of course keep the proposed syntax and let Scala Steward execute the `cs...
I do not yet understand why the custom heuristic is needed. I think the `groupId` heuristic would be able to update `platformVersion` above.
Ok, so the issue is that the `val` used for the version does not contain a word of the groupId or artifactId so Scala Steward can't associate `platformVersion` with the...
I would also focus on the simple cases and ignore the esoteric ones. I could imagine that the naive approach works for 95% or more of the cases where a...
Just a note: twirl-api must be a dependency in that project. Scala Steward wouldn't have tried updating it if that weren't the case. My guess is that it is added...
Scala Steward does not (yet) react to messages but there is the config option `updatePullRequests = "always"` which keeps the PR always in sync with the base branch via merges....
Scala Steward is a batch program and there is currently no way to influence its schedule. Maybe some day it will be a long-running server application where it would be...