Scala 3 dependency resolution in sbt manager #29082
Replies: 1 comment
-
Converted to issue: #29087 A PR would be very welcome, thanks. Usually, if a particular manager or ecosystem changes behavior in a new release then we consider it a feature request to support the new release, and only a bug fix if existing behavior all stopped working. In this case I assume that 2.x -> 2.x upgrades continue working. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Bitbucket
Please tell us more about your question or problem
Starting with scala 3, dependencies are published with major version.
Here is an example:
As you may see, for scala 3 there is only a major version. However if we have scalaVersion defined in build.sbt:
renovate bot attempts to resolve dependency with _3.4 prefix, can not find it via sbt manager and fallbacks to maven (which does not work in all cases, e.g. when library pushed without maven support).
Notes:
I can contribute the fix.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions