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

Verify that the Scala 3 LTS bugfix backport doesn't break anything #774

Closed
wants to merge 1 commit into from

Conversation

mzuehlke
Copy link
Contributor

As there isn't an artifact for Scala 3 LTS that includes scala/scala3#20171 I gave it a try with 3.4.2-RC1 that already contains scala/scala3#19737

This PR shows that the only thing that changes is the message returned form the compiler and not changes to munit are needed once Scala 3 LTS with the fix gets released.

As there isn't an artifact for Scala 3 LTS that includes scala/scala3#20171
I gave it a try with 3.4.2-RC1 that already contains scala/scala3#19737

This PR shows that the only thing that changes is the message returned form the compiler and not changes to munit are needed once Scala 3 LTS with the fix gets released.
@tgodzik
Copy link
Contributor

tgodzik commented Apr 26, 2024

The PR should be in the next LTS, I confirmed it with the team, they just have a lot on their plate currently.

mzuehlke added a commit to mzuehlke/munit that referenced this pull request Sep 30, 2024
Apply the learning from the older draft PR: scalameta#774

Closes: scalameta#834
Closes: scalameta#774
@tgodzik tgodzik closed this in #835 Sep 30, 2024
@mzuehlke mzuehlke deleted the scala-3.4.2-RC1 branch September 30, 2024 09:14
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 this pull request may close these issues.

2 participants