scalacenter / scalafix

Refactoring and linting tool for Scala

Home Page:https://scalacenter.github.io/scalafix/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

sbt-scalafix: support execution against files built with Scala 2.12.19 or 2.13.13

SethTisue opened this issue · comments

Pending scalameta/scalameta#3573 for semanticdb-scalac support.

A new scalafix release testing full compatibility will follow shortly (using, as well as supporting 2.13.13 also).

Note however that one could most likely use an existing sbt-scalafix release:

transparently if semanticdb-scalac is backpublished for 4.8.10

perhaps that's actually the plan? you could ask on scalameta/scalameta#3573

I'm publishing 2.13.13 to Maven Central right now

broadened to include 2.13.13, which is now on Maven Central, as per https://contributors.scala-lang.org/t/scala-2-13-13-release-planning/6315/17?u=sethtisue

I backpublished Scala 2.12.19 for 4.8.10, 4.8.15 and 4.9.0. Let me know, if anything more is needed!

not as far as I'm concerned! thanks

Oh, oops, what about 2.13.13...?

That's ongoing 😅 Seems that Scala 2.13.13 surfaced some warnings, so we haven't yet merged it. Will finish everything until tomorrow.

Done with Scala 2.13.13 for 4.7.8, 4.8.10, 4.8.15 and 4.9.0.

Thanks @tgodzik!

Impact of back-publishing validated through scalacenter/sbt-scalafix#389 & scalacenter/sbt-scalafix#390 👍

scalafix-testkit for Scala 2.13.13 and 2.12.19 does not available 😢

That's right, sorry for the confusion as this focused on supporting target files compiled with 2.12.19 & 2.13.13. I will update the title to be clearer.

The ability for rule authors build against these patches versions was merged in #1932, but because there is no backpublishing mechanism in Scalafix, it will only have effect in the upcoming Scalafix release (0.12.0), which is blocked by the release Scalameta 4.9.1 for a different reason (4.9.0 had a regression, which I identified by running a sanity check against your rules actually). This should be only a few days away.