Scala 2.13.13 release planning

SethTisue · January 22, 2024, 3:49am

Things are progressing. We’re down to four open PRs on the 2.13.13 milestone

With luck, we’ll have a release candidate in a week or so? Knock on wood.

SethTisue · January 22, 2024, 4:27am

Oh, I should have mentioned: we should hold 2.13.13 until 3.4.0 is released, so that 2.13.13 will be able to read 3.4 TASTy. 3.4.0-RC2 just came out, so we are optimistic that 3.4.0 won’t take too much longer.

GitHub issue is TASTy reader should support Scala 3.4 · Issue #12932 · scala/bug · GitHub

SethTisue · February 10, 2024, 12:50am

We are very nearly done winding down the 2.13.x PR queue for the release. We hope/expect to merge just one more PR (finalizing support for Scala 3.4 in the TASTy reader) and then announce a release candidate early next week.

SethTisue · February 10, 2024, 2:50am

Scala 2.13.13 draft release notes:

github.com

SethTisue/scala-dev/blob/scala-2.13.13/releases/2.13.13.md

# Scala 2.13.13

The Scala team at Lightbend is pleased to announce Scala 2.13.13.

The following changes are highlights of this release:

### Language

* Support binary integer literals using `0b`, as in Java ([#10656](https://github.com/scala/scala/pull/10656) by [@som-snytt](https://github.com/som-snytt))

### Compatibility

* TASTy reader: support Scala 3.4 ([#10670](https://github.com/scala/scala/pull/10670) by [@bishabosha](https://github.com/bishabosha))
* Support certain Java libraries compiled on JDK 21 ([#10675](https://github.com/scala/scala/pull/10675) by [@SethTisue](https://github.com/SethTisue))
* For JDK 22 support, upgrade to ASM 9.6 ([#10576](https://github.com/scala/scala/pull/10576) by [@Philippus](https://github.com/Philippus))

### Align with Scala 3

* Allow either `-Xsource:3` (for preparing to switch to 3) and `-Xsource:3-cross` (for crossbuilding on 2 and 3) ([#10573](https://github.com/scala/scala/pull/10573) by [@som-snytt](https://github.com/som-snytt))
* For migration to 3, accommodate case companion as function ([#10648](https://github.com/scala/scala/pull/10648) by [@som-snytt](https://github.com/som-snytt))

This file has been truncated. show original

If you have any suggested improvements to the notes themselves, you can comment on this pull request.

SethTisue · February 13, 2024, 4:05pm

The 2.13.13 release candidate is 2.13.13-bin-17c0c74. Please test!

https://stackoverflow.com/questions/40622878/how-do-i-use-a-nightly-build-of-scala has instructions on using Scala 2 nightlies.

Draft release notes at Scala 2.13.13 draft release notes by SethTisue · Pull Request #861 · scala/scala-dev · GitHub — feedback welcome.

We’ll allow a minimum of one week for testing, so we won’t release before Tuesday, February 20.

sjrd · February 15, 2024, 3:39pm

Scala.js 1.15.0 passes, although I had to turn fatal-warnings off in two projects. Sorry for the late testing.

vasilmkd · February 15, 2024, 10:56pm

I built the Scala Plugin for IntelliJ using 2.13.13-bin-17c0c74 and ran all tests against the RC. Everything went well. Thank you for the release.

som-snytt · February 16, 2024, 7:32am

I’m sorry another Valentine’s Day passed with no 2.14 release, but thank-you to the Scala Team Members at Lightbend for their continued attention.

Off now to read the latest “Lightbend Monthly” before bedtime.

SethTisue · February 21, 2024, 9:19pm

2.13.13 JARs are now on Maven Central.

Tooling and compiler plugin maintainer powers, activate! Please publish support.

We won’t announce before Friday, February 23, 2024.

sjrd · February 21, 2024, 9:32pm

Scala.js 1.15.0 for 2.13.13 is on its way to Maven Central.

I will do earlier versions tomorrow.

WojciechMazur · February 22, 2024, 9:46am

Scala Native 0.4.{13-17} compiler plugins for 2.13.13 are on their way to Maven Central

WojciechMazur · February 22, 2024, 10:49am

We’ve found a regression in compilation for scaladoc when using Scala 3 defined symbols. It might affect users publishing Scala 2.13 artifacts/documentation for projects using Scala 3 ADTs. It does not affect normal compilation.

github.com/scala/bug

Regression in scaladoc compilation when using in Scala 3 definitions

opened 10:46AM - 22 Feb 24 UTC

WojciechMazur

## Reproduction steps Scala version: 2.13.13 Tested with Scala 3 versions fo…r cross compiled project: 3.3.1 and 3.3.2 [reproduction-sbt.zip](https://github.com/scala/bug/files/14372699/repro.zip) run with `sbt "base/publishLocal; projectC/publishLocal"` 1. Define ADT in Scala 3, create a jar out of it ```scala package testlib enum ADT: case SingletonCase case ClassCase(x: String) ``` 2. Define Scala 2 project that uses Scala 3 JAR ```scala package app object Main { def main(args: Array[String]): Unit = { println(testlib.ADT.SingletonCase) println(testlib.ADT.ClassCase("foo")) } } ``` 3. Try to create documentation for Scala 2 project, (`sbt Compile/doc`) ## Problem Compilation fails with ``` error] stack trace is suppressed; run last projectC / Compile / doc for the full output [error] (projectC / Compile / doc) scala.reflect.internal.Types$TypeError: Unsupported Scala 3 generic tuple type scala.Tuple in bounds of type MirroredElemTypes; found in scala.deriving.Mirror.<refinement>. [error] Total time: 0 s, completed Feb 22, 2024, 11:42:57 AM ```

SethTisue · February 23, 2024, 3:51pm

I’ll mention the Scaladoc / TASTy reader regression in the release notes — doesn’t seem worth withdrawing the release over.

Most tooling is now in place, but not quite all, so no announcement today — perhaps Monday.

The JLine upgrade in 2.13.13 broke the console command in sbt. Eugene just released sbt 1.9.9 to fix it. I’ll mention in the release notes that 2.13.13 users should upgrade to 1.9.9 (if they want to use the REPL from sbt, anyway).

SethTisue · February 25, 2024, 8:21pm

Metals support is now in place and other key tooling has published, so it looks like we’re all set to announce first thing Monday (US West Coast time). Please raise any doubts soon if you have them.

mkurz · February 26, 2024, 2:25pm

Not sure what’s the actual Problem but upgrading Play to the latest Scala version makes MiMa raise an error:

github.com/playframework/playframework

Comment by mkurz - Upgrade to latest scala versions

playframework:main ← mkurz:scala_upgrades

@SethTisue Seems there is a problem... Not sure if MiMa needs to be adjusted? … If you run ``` sbt "Play / mimaReportBinaryIssues" ``` on this PR, you end up with: ``` [error] Play: Failed binary compatibility check against org.playframework:play_2.13:3.0.0! Found 3 potential problems (filtered 7) [error] * abstract method bindings(play.api.Environment,play.api.Configuration)scala.collection.Seq in class play.api.inject.Module does not have a correspondent in current version [error] filter with: ProblemFilters.exclude[DirectAbstractMethodProblem]("play.api.inject.Module.bindings") [error] * abstract method bindings(play.api.Environment,play.api.Configuration)scala.collection.Seq in class play.api.inject.Module does not have a correspondent in current version [error] filter with: ProblemFilters.exclude[DirectAbstractMethodProblem]("play.api.inject.Module.bindings") [error] * abstract method bindings(play.api.Environment,play.api.Configuration)scala.collection.Seq in class play.api.inject.Module does not have a correspondent in current version [error] filter with: ProblemFilters.exclude[DirectAbstractMethodProblem]("play.api.inject.Module.bindings") ``` It's complaining about: https://github.com/playframework/playframework/blob/adb41bde4efa62603a7b92bc3e2b7903ddc8cade/core/play/src/main/scala/play/api/inject/Module.scala#L61

@SethTisue maybe you can take a look what’s going on here? Thanks!

SethTisue · February 26, 2024, 10:12pm

The Play issue has been sorted out. We added some wordings to the release notes to even more strongly encourage users of -Xsource:3 to consider using -Xsource:3-cross instead.

SethTisue · February 26, 2024, 10:12pm

2.13.13 is now fully announced! Thanks to everyone who participated, even in the smallest way.

SethTisue · February 27, 2024, 6:40pm

Some library authors who were already using -Xsource:3 are getting MiMa failures when upgrading to 2.13.13 and switching from -Xsource:3 to -Xsource:3-cross. If you’re in this situation, you may need to wait for 2.13.14. See Case companions no longer extends FunctionN under `-Xsource:3-cross`, breaks binary compatibility · Issue #12961 · scala/bug · GitHub for details.

SethTisue · February 28, 2024, 2:09am

A new section of the Scala 3 Migration Guide documents -Xsource:3 and -Xsource:3-cross: Scala 2 with -Xsource:3 | Scala 3 Migration Guide | Scala Documentation

This is also now linked from the 2.13.13 release notes.

SethTisue · February 29, 2024, 12:08am

The new boolean-literals lint in 2.13.13 (see release notes) has been at least somewhat controversial; I suspect we will adjust it for 2.13.14. Y’all can give feedback on how you think we should proceed here: Demote -Xlint:named-booleans to -Wnamed-literal and tweak noise level by som-snytt · Pull Request #10704 · scala/scala · GitHub