This thread is for updates and discussions about an eventual Scala 2.13.6 release.
2.13.5 was released on February 22.
We’ll definitely need to do at least one release to update the TASTy reader, so perhaps that will end up being the determinant of the 2.13.6 release timing.
It seems the current 2.13.6 nightlies don’t support the TASTy format of 3.0.0-RC2 (3.0.0-RC2 is at 28.0.3, while 2.13.6-bin-8356365 is at 28.0.1). Is that expected? Is a bump of the format to 28.0.3 planned in 2.13.x, and in 2.13.6 in particular?
In more detail, I’m getting the following error when using 3.0.0-RC2 libraries from Scala 2.13.5 or 2.13.6-bin-8356365:
Hi, Yes I am working on an update for Scala 2.13.6 to support the changes to TASTy and erasure rules in Scala 3.0.0-RC2, there is also planned another breaking change to TASTy coming in 3.0.0 which is to bump the TASTy version to its first ever final release.
Thanks! For the context, I ran into this error when trying to update the branch of this PR to 3.0.0-RC2 (discussed in https://contributors.scala-lang.org/t/porting-ammonite-to-dotty). It uses Scala 2 libraries from Scala 3 and the other way around too, so the tasty format has to match exactly. As soon as a 2.13 nightly for tasty 28.0.3 is available, it should be possible to update to 3.0.0-RC2 (and merge this PR, at last).
It seems likely that Scala 3.0 final will come out soon (at least, I haven’t heard anything about a need for an RC4…?), so we’ll do 2.13.6 soon afterwards, with Jamie’s TASTy reader update and whatever other PRs we can manage to get over the finish line.
3.0 is expected later this week and 2.13.6 is targeted for Monday, May 17 (tentatively, but we wouldn’t let it slip very far) and the release lead is Lukas. The scala/bug and scala/scala milestones have been updated; every scala/scala PR on the milestone is labeled with “prio:blocker”, “prio:hi”, or blank which means would-be-nice.