Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 08:05
    alejandrohdezma commented #2952
  • 07:17
    alejandrohdezma commented #2952
  • Jan 30 19:51
    egaxhaj commented #2952
  • Jan 30 19:14
    mzuehlke commented #2952
  • Jan 30 18:08
    egaxhaj opened #2952
  • Jan 30 15:13
    codecov[bot] commented #2951
  • Jan 30 14:59
    codecov[bot] commented #2951
  • Jan 30 14:17
    fthomas milestoned #2951
  • Jan 30 14:17
    fthomas milestoned #2951
  • Jan 30 14:17
    fthomas labeled #2951
  • Jan 30 14:17
    fthomas opened #2951
  • Jan 30 14:16

    fthomas on simplify-ProcessAlg

    Simplify ProcessAlg This simpl… (compare)

  • Jan 30 11:35
    fthomas labeled #2950
  • Jan 30 11:35

    fthomas on main

    Update Scala version to 3.2.2 Merge pull request #2950 from K… (compare)

  • Jan 30 11:35
    fthomas closed #2950
  • Jan 30 11:23
    Kordyjan opened #2950
  • Jan 29 18:28

    fthomas on bsp

    Rename function to create an Ex… (compare)

  • Jan 29 16:09

    fthomas on bsp

    Handle artifactIds with cross b… (compare)

  • Jan 29 10:14
    fthomas commented #2640
  • Jan 29 09:46
    lefou commented #2640
Naftoli Gugenheim
@nafg
You're on the "For you (beta)" tab?
Arunav Sanyal
@Khalian
Yea I am. I presume that's gonna be completely cluttered with scala steward updates then?
Naftoli Gugenheim
@nafg
Click Filter at the top
Also Send feedback ;)
under Filter turn of Repositories seems to work for me
(I never use the main github page though)
Arunav Sanyal
@Khalian
@nafg Thanks. I think I am going to drop an issue somewhere for github for this.
Naftoli Gugenheim
@nafg
Or just don't use the "For you" tab
Click Send feedback ;)
It is Beta after all
But also, maybe scala steward could identify itself as a bot somehow
Markus Appel
@markusa380
So after looking at the code of Scala Steward, it looks like all it does is get libraryDependencies of the root project to look at - how can I make it update a subproject that the root project .dependsOn?
Naftoli Gugenheim
@nafg
@markusa380 that doesn't sound right
Markus Appel
@markusa380
@nafg I have a subproject that is only referenced through a .dependsOn in the root project. And it's dependency is not updated. And looking at the code I see no reason for it to be updated. I would like to be proven wrong of course.
Naftoli Gugenheim
@nafg
Public GitHub? I'm curious, can you link?
Tobias Roeser
@tobiasroeser:matrix.org
[m]
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.
Naftoli Gugenheim
@nafg
@tobiasroeser:matrix.org do you know about https://github.com/kitlangton/scala-update ?
not sure if that meets your goal
Naftoli Gugenheim
@nafg
Is the VirtusLab scala steward instance working properly?
Also, what's the Scala Steward GitHub App?
4 replies
eikek
@eikek
Hello, is it possible to have scala-steward create a single PR with all the updates?
15 replies
eikek
@eikek:matrix.org
[m]
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!
Naftoli Gugenheim
@nafg
What's with creating all the revert commits instead of just force-pushing a clean branch?
Naftoli Gugenheim
@nafg
Like it used to do
Kilic Ali-Firat
@alifirat

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 saying
Failed 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?

Tobias Roeser
@tobiasroeser:matrix.org
[m]
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?
Frank Thomas
@fthomas
@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
Tobias Roeser
@tobiasroeser:matrix.org
[m]
@fthomas: Thank you!
Kilic Ali-Firat
@alifirat
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 ?
Frank Thomas
@fthomas
@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
Naftoli Gugenheim
@nafg
Why does it have a v?
7 replies
Frank Thomas
@fthomas