-
Notifications
You must be signed in to change notification settings - Fork 88
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
Scala 3.3.3, 2.13.13, 2.12.19 #660
Conversation
I didn't go to 2.13.14 because I'd have to upgrade Scala.js as well and we seek to avoid doing that in this repo unless we must, for maximum compatibility going from Scala 3.2 to 3.3 might seem inconsistent with that, but I think we should do it, because all of the messaging around Scala 3 has been super consistent that 3.3 is the first LTS and older versions are dead. plus 3.3 isn't at all new anymore.
Thanks @SethTisue. Do we have plan to make a new release after this update? |
Nothing substantive has been merged since 2.12.0, so I don't see a reason to. |
Oh, there's #658. We could release after that one. |
Thanks @SethTisue. Since JDK 21 support is added into 2.12.18, this upgrade (and next release) really helps downstream projects to simplify Scala dependencies. |
hmm, but I don’t think it does; it doesn’t matter in the slightest to downstream users whether we upgraded our Scala version here or not I think you may have incorrect ideas about how these things work. |
Do you mean we shouldn't pull in Scala dependencies from this project? |
@manuzhang I don't understand your question |
@SethTisue Never mind. Any plan to make a new release soon? |
Hmm, I guess we could do one, yeah — but the motivation would be to ship #658, and not anything having to do with this PR. Is that the reason you're interested in a new release, or do you have some other reason in mind? |
2.13.0 (https://github.com/scala/scala-collection-compat/releases/tag/v2.13.0) is on its way to Maven Central. (release job: https://github.com/scala/scala-collection-compat/actions/runs/12993856393 ; I had to redo our Sonatype secrets to use the user token, as Sonatype now requires) |
I didn't go to 2.13.14 because I'd have to upgrade Scala.js as well and we seek to avoid doing that in this repo unless we must, for maximum compatibility
going from Scala 3.2 to 3.3 might seem inconsistent with that, but I think we should do it, because all of the messaging around Scala 3 has been super consistent that 3.3 is the first LTS version and older versions are dead. besides, 3.3 isn't at all new anymore.