3.4.0-RC3 and RC4 are ready for testing! Both compiler versions were available on Maven Central for a few days already. I was waiting with the announcement until we were sure that there were no problems in tooling directly using the compiler.
RC3 fixes the minor forward compatibility issue mentioned earlier and aligns the context bounds treatment under the -3.4-migration setting with the standard behavior.
RC4 is identical, but it bumps a version of jsoup - a dependency of scaladoc. The previous version was affected by a CVE. Copying my comment from the 3.3.2 thread:
The mentioned CVE is CVE-2022-36033 . In our case, it is absolutely not exploitable in any way. However, we treat such things seriously, so we decided to release 3.3.2-RC3 and 3.4.0-RC4, being identical to the previous release candidate but having jsoup dependency bumped to not vulnerable version.
Noted with thanks. Is there any way I can do a quick test, as I would need to make sure that is the only problem that is causing our internal library to break in Scala 3.4.x.
I understand 3.4.0 will be released anytime soon, and its release has been tracked here extensively, but I see no information on what is 3.4.1.
When is 3.4.1 expected to be released, given it already has RC now?
When will fixes from 3.4.1 be released in LTS, like 3.3.3 or whatever?
I am not much interested in any new language features, but my project fails to compile with 3.3.1 at the moment and corresponding fixes seem to be present in 3.4.1-RC1.
I see. Feel free to comment on the PR and mention that you’re hoping it will be backported, with any supporting information. I see it’s marked as “needs assessment” for backporting — that assessment will presumably happen after the team is all done with 3.3.2 and 3.4.0.
(Whether there might be some technical barrier to backporting, I have no idea.)
The issue is already listed in Scala 3.3 LTS backports · GitHub as Needs Assessment. I made a comment in it. If there is some work I could do to help the backport, I will be glad to do it (prepare a PR or whatever is needed - I have no idea how backporting works in practice).
Can we add a line to the release notes that indicates that this release is not an LTS release, and perhaps a link to information regarding that? As well as perhaps linking to the release blog? We’ve already seen confusion on this matter at our work.
Same issue is present in VS Code with Metals. It’s causing worksheets to not evaluate when using 3.4.0 (I think that’s the reason?)
I get this in Metals:
2024.03.02 21:09:05 INFO Failed to resolve mtags for 3.4.0
Hey, from 3.4.0 mtags are longer be released for metals, and they rely on presentation compiler provided by dotty. There should be another log below saying: Presentation Compiler found for 3.4.0
Despite that, worksheets should work for you, so if you don’t mind sharing the snippet in direct message, that caused the failure or provide any more information I’ll be glad to help solve this issue.
just got 3.4.0 from SDKMAN.
