New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group artifacts that need to be upgraded together #2459
Comments
Maybe
It does not upgrade dependencies together, but can wait until related dependency release.
It would be helpful if updating this entry is added in |
For most of the sbt-scalafix usages (using rules, not defining them), upon a new Scala release, sbt-scalafix should be bumped before Scala, so that semanticdb support for the upcoming release is ready. The new Scala 2.x release process fixes that since sbt-scalafix PRs are opened ahead of the Scala PRs (provided a new release of sbt-scalafix is tagged fast enough) because of the Scala embargo in In your case, the bump of sbt-scalafix and scala must be done atomically because you define rules in the project (the missing full cross-build artifact missing is scalafix-testkit). So I am not sure adding sbt-scalafix to In both cases, for Scala 3.x, there is no problem as the support for generating semanticdb files is baked-in in the compiler. |
If the Scala versions used in the scalafix modules of your build were coming from sbt-scalafix, there wouldn't be a problem since the sbt-scalafix bump could be merged independently of the Scala bump for the rest of the modules. I guess it won't be easy as-is as the build uses the built-in
|
A classic case of this is
scalafix
and the exact Scala version that matches.For example, an update like
scalafix
cannot occur without Scala2.13.8
which is not formally released yet - ekrich/sconfig#228I don't know if this is possible but it would really help at least in this case.
The text was updated successfully, but these errors were encountered: