Renovate: MR grouping not working with sbt

Created on 8 Jul 2020  路  5Comments  路  Source: renovatebot/renovate

What Renovate type are you using?

Self hosting Renovate.

Describe the bug

Given the following build.sbt file:

val cucumberVersion = "6.2.0"

libraryDependencies ++= Seq(
  "io.cucumber" %% "cucumber-scala" % cucumberVersion % Test,
  "io.cucumber" % "cucumber-junit" % cucumberVersion % Test,
  "io.cucumber" % "cucumber-picocontainer" % cucumberVersion % Test
)

When RenovateBot runs, it correctly detects and suggest to update the version in cucumberVersion variable but the summary of the MR (and the title as well) only mentions one library update:

image

I've seen in Maven projects that the 3 libraries are grouped as a single MR and I would expect the same behavior for sbt projects.

Relevant debug logs

N/A

To Reproduce

Use sample above.

Additional context

N/A

sbt priority-3-normal reproduced

Most helpful comment

Done here, I used the sample provided by @gaeljw : https://github.com/bursauxa/renovate-issue-6706

I configured renovate with the Github app and next-next-next for settings.

Notice the multiple pull requests: https://github.com/bursauxa/renovate-issue-6706/pulls

All 5 comments

In addition, renovate will create one MR for each library that is updated by the variable change (that would be 3 separate MRs in the example provided).

@bursauxa can you create a minimal reproduction repo on github.com that we can use to test against?

Done here, I used the sample provided by @gaeljw : https://github.com/bursauxa/renovate-issue-6706

I configured renovate with the Github app and next-next-next for settings.

Notice the multiple pull requests: https://github.com/bursauxa/renovate-issue-6706/pulls

:tada: This issue has been resolved in version 23.84.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

Just had my first joint renovate MR popping up in Gitlab, thanks @rarkins ! :+1:

Was this page helpful?
0 / 5 - 0 ratings