Skip to content
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

Please publish for Scala 2.12.20 #2064

Closed
SethTisue opened this issue Sep 2, 2024 · 5 comments · Fixed by #2052
Closed

Please publish for Scala 2.12.20 #2064

SethTisue opened this issue Sep 2, 2024 · 5 comments · Fixed by #2052

Comments

@SethTisue
Copy link
Contributor

...which is now on Maven Central, as per https://contributors.scala-lang.org/t/scala-2-12-20-release-planning/6580/8

@tgodzik
Copy link
Contributor

tgodzik commented Sep 2, 2024

I am working on releasing scalameta https://github.com/scalameta/scalameta/pull/3951/files which versions would be needed for scalafix?

@bjaglin
Copy link
Collaborator

bjaglin commented Sep 2, 2024

@tgodzik the latest Scalafix version brings Scalameta 4.9.3 - we have been stuck on this for a while (see description of #2047 - independently of Scala 2.12.20, do you know when you will tag 4.9.10?)

@tgodzik
Copy link
Contributor

tgodzik commented Sep 3, 2024

semanticdb for 4.9.3 should be available, as for 4.9.10 I am not sure, I think once the scalafmt relevant changes are done.

@bjaglin bjaglin linked a pull request Sep 3, 2024 that will close this issue
2 tasks
@bjaglin
Copy link
Collaborator

bjaglin commented Sep 3, 2024

sbt-scalafix 0.12.1 supports sources in 2.12.20 thanks to the cross-publishing of scalameta 4.9.3 👍

Since publishing is not urgent (only for rule authors), I'll wait for 2.13.15 (and probably 3.3.4) for scalafix 0.12.2.

@SethTisue
Copy link
Contributor Author

SethTisue commented Sep 4, 2024

okay — I'll open a new ticket once 2.13.15 is published. thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants