Thats just one. My github page is flooded by these. I dunno if github is doing this or scala steward. The three dots on the side suggest either flagging scala steward for abuse or blocking the user entirely from contributing, neither of which I want.
You're on the "For you (beta)" tab?
Also Send feedback ;)
under Filter turn of Repositories seems to work for me
(I never use the main github page though)
Click Send feedback ;)
It is Beta after all
But also, maybe scala steward could identify itself as a bot somehow
Hi. Is it possible to let scala-steward run locally but not create pull request to any remote server? Creating local branches would be fine though.
not sure if that meets your goal
I was trying scala-update, but it somehow can't detect any outdated versions, but sbt-update (the sbt plugin) does detect lots of it. Didn't think about renovate yet and the custom branch for scala-steward could also work. All very good hints. Thank you!
Hello, I'm using the latest version of Scala Steward (0.16.0) published this week. I see an error that seems internal but I'm not sure at 100%. With the following settings
pullRequests.grouping = [
{ name = "all", "filter" = [{"group" = "*"}]},
{ name = "patches", "filter" = [{"version" = "patch"}] }
]I get a parsing error from one of the JSON persisted in the workspace sayingFailed to parse or decode JSON from /opt/docker/workspace/store/pull_requests/v2/github/ContentSquare/de_steward-test-repository/pull_requests.json
I've tried to cleanup the workspace and try again but I'm still getting the issue. Maybe the configuration I've set are incompatible?
Just a short question about stewards internals. Is it correct, that scala-steward does not differentiate between dependency scopes like
compile, runtime, test, ...?
The mill plugin currently only extracts the compile deps, and I'd like to add the other scopes too.
Can I just add them, or do I need to set some extra flags somewhere?
@tobiasroeser:matrix.org You can just add them. SbtAlg puts the scope into
Dependency#configurations if it is something other than compile. For test dependencies the PR body will then be labeled differently: https://github.com/scala-steward-org/scala-steward/blob/d3e22af810fa71b8917fd47e5ba128b461b8b197/modules/core/src/main/scala/org/scalasteward/core/vcs/data/NewPullRequestData.scala#L257-L267
Hey, small question about how Steward is find new version for a library. I'm using the 0.16.1 and time to time, Steward is creating PRs that downgrade the version from v3.2.3 to 3.0.3. Is due to the prefix
v in the library version? I tried to check in the codebase but I didn't find the code that handles this part, is it based on timestamp ?
@alifirat Ordering of versions and selecting the next suitable version is done in https://github.com/scala-steward-org/scala-steward/blob/main/modules/core/src/main/scala/org/scalasteward/core/data/Version.scala You can test this interactively with this Scastie: https://scastie.scala-lang.org/6cTFqY3dTmGbZIIEgM6lyQ
3 replies
https://scastie.scala-lang.org/q0mGpVC5RZq19lkLXGDpOA shows that v3.2.3 is less than 3.0.3