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.

Sign up for GitHub

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

Jump to bottom

Tweak 3.4.3 blog post #1687

Merged
merged 1 commit into from
Aug 23, 2024
Merged

Tweak 3.4.3 blog post #1687

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _posts/2024-08-23-release-notes-3.4.3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,14 @@ title: "Scala 3.4.3 is now available!"
---
Scala 3.4.3 is now available!

The hotfix version 3.4.3 is recommended for library authors who cannot or do not want Scala 3.5 upgrade, but want to keep their forward and backward binary compatibility.
The hotfix version 3.4.3 is recommended for library authors who cannot or do not want to upgrade to Scala 3.5, but want to keep their forward and backward binary compatibility.

We expect that only a few library authors will be affected, because:

- most library authors are using the Scala 3.3 LTS series. Staying on LTS is our standard recommendation for library authors.
- the issue is specific to match types that are exposed in APIs

This release reverts changes introduced in Scala 3.4.2 that led to binary incompatibility of match types produced by the compiler. You can read about this issue in [Scala 3 repository](https://github.com/scala/scala3/issues/21258). The new behaviour would be restored in some next major version (probably 3.6) after being well described and probably introducing a warning for the users.
This release reverts changes introduced in Scala 3.4.2 that led to binary incompatibility of match types produced by the compiler. You can read about this issue in the [Scala 3 repository](https://github.com/scala/scala3/issues/21258). The new behaviour will be restored in some next major version (probably 3.6) after being well described and probably introducing a warning for the users.

We recommend authors of Scala 3 libraries that use match types in their APIs to set up [TASTy MiMA](https://github.com/scalacenter/tasty-mima) checks as the extension to classic bytecode-based MiMa binary compatibility assertions.

Expand Down