Please publish for Scala 2.13.12

[SethTisue]

...which is now on Maven Central, as per https://contributors.scala-lang.org/t/scala-2-13-12-release-planning/6217/26

[bjaglin]

Thanks for the ping!

FTR, from the discussion in discord:

for 99,999% of the users, the only benefit of publishing a new "scalafix release" in sync with each new scala 2.x patch release is for sbt-scalafix (which currently has a coupled release cycle with scalafix, see #1146) to automatically bring-in a release of scalameta that has a semanticdb-scalac available for that version (via the semanticdbVersion := scalafixSemanticdb.revision recommendation in the docs).

However,

• The user could just update to the latest manually. I am actually planning to tweak in sbt-scalafix the error messages related to a missing semanticdb-scalac to reduce the impact of the new publishing policy of scalameta (see https://discordapp.com/channels/632642981228314653/632642981228314657/1131223392679378994 / Update scalameta to 4.8.8 #1846 (comment))
• As @tomasz Godzik mentioned, semanticdb-scalac is now backpublished. That said, we happen to be on an old 4.7.x scalameta version in the latest scalafix release (funny enough, due to lack of time on my side for that scalameta publishing change described above). And it turns out that the backpublishing was not done, so this time around we would need a new release anyway 🤷‍♂️

So I'll publish a new sbt-scalafix/scalafix release by Monday (official release of 2.13.12), but the next scala 2.x release won't really need a embargo-synchronized scalafix release considering the 2 items below shouuld be "solved" by then.

[bjaglin]

the next scala 2.x release won't really need a embargo-synchronized scalafix release considering the 2 items below shouuld be "solved" by then.

I just got an exception that proved me wrong 😅 It turns out that 2.13.12 has a "breaking" change that makes one rule regress as it depends too much compiler internals (through semanticdb diagnostics), so we can't guarantee this won't happen again next time... But at least we can check during the embargo period, and decide not to release anything right away if built-in rules don't need to be updated.