# The Scala Programming Language

Published articles for The Scala Programming Language.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Security advisory: update your JDK (CVE-2026-114938, "Java4Shell")

DevFeed: [Security advisory: update your JDK (CVE-2026-114938, "Java4Shell")](<https://devfeed.tech/articles/security-advisory-update-your-jdk-cve-2026-114938-java4shell-142371.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/jdk-java4shell-vulnerability.html>)

Published: 2026-11-17T23:00:00Z

Content type: tutorial

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [saml](<https://devfeed.tech/topics/saml.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [arm](<https://devfeed.tech/tags/arm.md>), [avx](<https://devfeed.tech/tags/avx.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-graviton](<https://devfeed.tech/tags/aws-graviton.md>), [base64](<https://devfeed.tech/tags/base64.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [ci](<https://devfeed.tech/tags/ci.md>), [crash](<https://devfeed.tech/tags/crash.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [decode](<https://devfeed.tech/tags/decode.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [security](<https://devfeed.tech/tags/security.md>), [security-advisory](<https://devfeed.tech/tags/security-advisory.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

CVE-2026-114938 ("Java4Shell") is a HotSpot JIT heap buffer overflow in the AVX-512 Base64 decoder. Crafted Base64 input can crash a JVM and, in some cases, enable unauthenticated remote code execution. The excerpt identifies affected systems as unfixed JDK 17.0.6 or later, 21, 25, or 27 running on x86-64 with AVX-512 VBMI and decoding attacker-controlled Base64; JDK 8 and 11 and ARM machines are described as unaffected. Update to a vendor-fixed build, checking the vendor and platform release status; container JDKs and CI installations need separate attention, and Linux distributions may backport fixes. Until an update is available, `-XX:-UseBASE64Intrinsics` disables the vulnerable optimized decoder across platforms, with possible slowdown for Base64-heavy workloads. The excerpt gives JVM-wide and Scala tool-specific ways to set the flag and says to remove it after updating.

### Source excerpt

On 2026-11-17, OpenJDK published a vulnerability advisory for CVE-2026-114938, also known as "Java4Shell" (CVSS 4.0: 9.2, Oracle's CVSS 3.1: 8.1). It is a heap buffer overflow in the HotSpot JIT's AVX-512 Base64 decoder on x86-64. An attacker who can send crafted Base64 input to a JVM can crash it, and in some cases run code remotely, with no authentication needed. Base64 is everywhere: HTTP Basic auth headers, JWTs, SAML, file uploads, and more. This is not a Scala issue, but it affects every application running on the JVM, including Scala ones. Server-side applications that decode untrusted input are the most exposed. Am I affected? You are affected if all of the following are true: you run JDK 17.0.6 or later, 21, 25, or 27 without the fix (see the table below). JDK 8 and 11 are not affected; on an x86-64 CPU with AVX-512 VBMI support (Intel Ice Lake or newer server CPUs, AMD Zen 4 or newer). ARM machines, including Apple silicon and AWS Graviton, are not affected; your application decodes Base64 input that an attacker can control. If you're unsure, assume you are affected. Many cloud servers and CI runners use CPUs with AVX-512. To check your JDK version and CPU on Linux: $ java -version openjdk version "17.0.21" 2026-10-20 ... $ grep -o 'avx512vbmi' /proc/cpuinfo | head -1 avx512vbmi If java -version shows an affected version and the second command prints avx512vbmi, the vulnerable code can run on that machine. Updating to the fixed JDKs The real fix is to update your JDK. As of 2026-11-18, the fixed builds are: JDK Oracle Corretto Temurin, Zulu, Microsoft, Red Hat JDK 17 17.0.21.1 17.0.21.1.2 not yet JDK 21 21.0.13.1 21.0.13.1.2 not yet JDK 25 25.0.5.1 25.0.5.1.2 not yet JDK 27 27.0.1.1 27.0.1.1.4 not yet Other vendors have not yet released fixed builds, or have not confirmed them at the time of this blog post being written. Check your vendor's advisory, and use the workaround below until a fix is out. Standalone JDKs (for example, ones installed via Coursier,

## Scoverage Hardening in Scala 3: Results and Next Steps

DevFeed: [Scoverage Hardening in Scala 3: Results and Next Steps](<https://devfeed.tech/articles/scoverage-hardening-in-scala-3-results-and-next-steps-140143.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/11/17/scoverage-hardening-results.html>)

Published: 2026-11-16T23:00:00Z

Content type: article

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [future](<https://devfeed.tech/tags/future.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [results](<https://devfeed.tech/tags/results.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Scala 3 coverage testing now runs across an expanded compiler test suite and on every pull request. As of early October 2026, 7,793 of 7,828 cases passed (99.55%); the effort fixed 95 breakages and identified a systematic cause for the remaining failures as future work. Scala 3's compiler instruments code after type checking using effectful probes, while Scoverage libraries provide reports; instrumentation uses `-coverage-out:DIR` and does not require a separate compiler plugin. Because probes can change behavior if they disrupt evaluation order, the compiler must preserve that order when instrumenting expressions. Testing was expanded incrementally across language test groups, with failures tracked, investigated, and passing tests restored as regression coverage. Nightly and release builds also compile selected projects with coverage. The article says the early instrumentation phase interacts with many later compiler phases, especially capture calculus, and suggests exploring instrumentation later in the pipeline to reduce those interactions.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: Scoverage hardening. The work is coordinated by the Scala Center. Summary We've been working throughout 2026 on making Scoverage more reliable in Scala 3. As the project comes to a close, this article reports on the results. We have successfully enabled coverage testing across the wider compiler test suite, fixed breakages encountered in process achieving a 99.5% pass rate, and for the 0.5% tests not working with coverage yet, identified a systematic root cause to be resolved as future work. What is coverage? Suppose you have a function that calculates a shipping fee: def shipping(total: Int): Int = if total >= 50 then 0 else 5 And a test: assertEquals(shipping(70), 0) The test passes, but it only tests the free shipping case. The paid-shipping branch never runs. Code coverage makes such gaps visible by recording which statements and branches execute during a test run. In this example, adding assertEquals(shipping(20), 5) would test the missing branch. In Scala 3, coverage instrumentation is built directly into the compiler. You can enable it with the -coverage-out:DIR compiler option, where DIR is the directory where you'd like coverage telemetry to be recorded. The compiler writes a map of instrumented statements, and the instrumented program records which of them execute at runtime. The Scoverage plugin and reporting libraries provide the reporting and visualization of this data. In Scala 3, the instrumentation itself comes from the compiler, so a separate compiler plugin is not needed. See Code Coverage for Scala 3 for documentation. You can visualize the reports as HTML using sbt-scoverage. Interactions with the language The compiler implements coverage as a phase that rewrites the program after type checking. This phase records statement execution by injecting probes before each. Probes are effectful function calls performing the recordings. Every later compiler phase then receives t

## Scala 3.10.1 is now available!

DevFeed: [Scala 3.10.1 is now available!](<https://devfeed.tech/articles/scala-3-10-1-is-now-available-128974.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.10.1/>)

Published: 2026-11-10T23:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [releases](<https://devfeed.tech/topics/releases.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>)

Tags: [asm](<https://devfeed.tech/tags/asm.md>), [change](<https://devfeed.tech/tags/change.md>), [cli](<https://devfeed.tech/tags/cli.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [directives](<https://devfeed.tech/tags/directives.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [java-17](<https://devfeed.tech/tags/java-17.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [jdk-28](<https://devfeed.tech/tags/jdk-28.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [lock](<https://devfeed.tech/tags/lock.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [nested](<https://devfeed.tech/tags/nested.md>), [package-private](<https://devfeed.tech/tags/package-private.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [sip](<https://devfeed.tech/tags/sip.md>)

### AI overview

Scala 3.10.1 adds JDK 28 compiler and class-file support, including target version 28, which cannot exceed the JDK running the compiler. It warns about calling `synchronized` on Java value-based class instances, which JDK 28 rejects; the release recommends a dedicated lock object. The bundled Scala CLI is upgraded to 1.18.0: its JVM launcher now requires Java 17 or newer, though code can still target older JVMs with options such as `--jvm 8` or `--jvm 11`. The release also adds experimental SIP-77 method-block end markers, enabled by import or compiler option; markers must match the method name at the call site, and the feature may change or be removed. Other changes include a new broad-catch warning, REPL resource support, and fixes across compiler and tooling.

### Source excerpt

Scala 3.10.1, the first patch release in the Scala 3.10 series, is now available. Release highlights JDK 28 support (#27347) The compiler now supports JDK 28, including target version 28 for -release and -java-output-version. The target version cannot exceed the JDK version running the compiler. ASM has also been updated to 9.11.1 (#27363), enabling support for JDK 28 class files. The compiler now warns when synchronized is called on an instance of a Java value-based class (#27128). JDK 28 rejects such calls. Use a dedicated lock object instead. Upgrade to Scala CLI 1.18.0 (#27255) The bundled Scala CLI has been upgraded from 1.17.1 to 1.18.0. Highlights include: The JVM launcher no longer starts on JDK 11-16 by downloading JDK 17 and relaunching. Start it on Java 17 or newer. Your code can still be compiled and run on older JVMs, for example with --jvm 8 or --jvm 11. scala fix removes deprecated comma separators from //> using directives. Java snippets, Java source read from standard input, and Java blocks in Markdown now support enums, records, package-private classes, and JEP 512 compact source files. See the Scala CLI 1.18.0 release notes for the full list of changes. Experimental SIP-77: method block end markers (#24251) Method block end markers make it easier to see where nested argument blocks end. Experimental SIP-77 lets you close an argument block introduced by : with a named end marker. The marker must name the method as it is written at the call site, so a mismatched name is an error. This feature is experimental and may change or be removed depending on the SIP Committee's decision. We welcome feedback from users who try it. Enable it with import scala.language.experimental.methodBlockEndMarkers or -language:experimental.methodBlockEndMarkers. //> using scala 3.10.1 //> using options -language:experimental.methodBlockEndMarkers def test(name: String)(body: => Unit): Unit = println(s"Running test: $name") body def repeat(times: Int)(body: => Unit): Unit

## Scala 3.3.9 LTS is now available!

DevFeed: [Scala 3.3.9 LTS is now available!](<https://devfeed.tech/articles/scala-3-3-9-lts-is-now-available-105424.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.3.9/>)

Published: 2026-10-27T23:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [JEP-401](<https://devfeed.tech/topics/jep-401.md>)

Tags: [backports](<https://devfeed.tech/tags/backports.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [classes](<https://devfeed.tech/tags/classes.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [doc](<https://devfeed.tech/tags/doc.md>), [higher-kinded-types](<https://devfeed.tech/tags/higher-kinded-types.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [java](<https://devfeed.tech/tags/java.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [lts](<https://devfeed.tech/tags/lts.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [series](<https://devfeed.tech/tags/series.md>), [support](<https://devfeed.tech/tags/support.md>), [syntax](<https://devfeed.tech/tags/syntax.md>)

### AI overview

Scala 3.3.9 LTS backports most bug fixes and some improvements from Scala 3.9.0. Compatibility was checked across more than 1,500 projects in the Scala 3 Open Community Build, with the changes reported not to break binary or source compatibility. Highlights include smaller Scaladoc jars by removing custom fonts, improved Java generic signatures for higher-kinded types and value classes, exhaustiveness checking for sealed abstract Java classes, clearer missing-member diagnostics, warnings for dubious negative literal syntax, and a Scaladoc fix for an NPE on JDK 25. The 3.3.x series is planned to receive support for the next year; eligible fixes and improvements from Scala Next will continue to be backported.

### Source excerpt

Scala 3.3.9 LTS is now available! This patch release backports most of the bugfixes and some of the improvements introduced in Scala 3.9.0. All of the backported changes were proven to not break either binary or source compatibility, by testing over 1500 projects in the Scala 3 Open Community Build. Notable changes Stop using custom fonts for Scaladoc, to reduce doc jar size #26393 Improve Java generic signatures for higher-kinded types, value classes #25540 #25744 #25631 Exhaustiveness checking for sealed abstract Java classes #25788 Actionable diagnostic for missing members #23572 Warn on dubious negative literal syntax (- 42, -42.abs) #24163 Scaladoc no longer crashes with an NPE on JDK 25 #25779 For a full list of changes and contributor credits, please refer to the release notes. Scala LTS Release Notice The next planned LTS 3.3 release will include updates introduced until last Scala 3.10.x before 3.11. We'll continue to backport eligible bug fixes and improvements from the Scala Next series. Because the next LTS 3.9.0 has now been released, we will continue to support the 3.3.x series for the next year. Scala 3.x End of service 3.3.x 2027 Sep 3.9.x 2029 Sep or later 3.10.x Until 3.11.x

## Security advisory: update your JDK (CVE-2026-91403)

DevFeed: [Security advisory: update your JDK (CVE-2026-91403)](<https://devfeed.tech/articles/security-advisory-update-your-jdk-cve-2026-91403-96146.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/jdk-certificate-vulnerability.html>)

Published: 2026-10-21T22:00:00Z

Content type: news

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve](<https://devfeed.tech/tags/cve.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [jdk-27](<https://devfeed.tech/tags/jdk-27.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [scala](<https://devfeed.tech/tags/scala.md>), [security](<https://devfeed.tech/tags/security.md>), [security-advisory](<https://devfeed.tech/tags/security-advisory.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

OpenJDK's CVE-2026-91403 advisory concerns eight compromised intermediate CA certificates shipped with JDKs across versions 8, 11, 17, 21, 25 and 27. The document identifies JDK 27.0.1, 25.0.5, 21.0.13, 17.0.21, 11.0.33, 8u512 and earlier as affected, including JVM applications and build tools that use the JDK's certificates. To check a JDK, it recommends running eed3si9n/emudhra-emsign-check locally or calling CheckCompromisedCa.test in CI; network errors can also cause the check to fail. As a temporary measure, it gives 16 SHA-256 fingerprints to append to blocked.certs for JDK 11+ or blacklisted.certs for JDK 8, then recommends verifying the certificates are blocked. The longer-term guidance is to install the latest fixed JDK patch and update all local, CI and Docker JDKs. Linux distribution JDKs typically use system CA certificates, so updating those may suffice; FreeBSD and Homebrew packages require direct updates.

### Source excerpt

On 2026-10-21, OpenJDK published a vulnerability advisory for CVE-2026-91403 (CVSS 9.1), which concerns eight compromised intermediate CA certificates shipped with the JDK. It affects all supported JDK lines: 8, 11, 17, 21, 25 and 27. This is not a Scala issue, but it affects every application running on the JVM, including Scala ones, as well as Scala build tools that use the JDK's certificates to download dependencies. Am I affected? You are affected if you use JDK 27.0.1, 25.0.5, 21.0.13, 17.0.21, 11.0.33, 8u512, or earlier. To check if your JDK is vulnerable, checkout eed3si9n/emudhra-emsign-check on your local machine, or call CheckCompromisedCa.test from your CI. $ sbt run [info] welcome to sbt 1.13.0 (Azul Systems, Inc. Java 1.8.0_402) [info] running main Java 1.8.0_402 (/Users/xxx/.sdkman/candidates/java/zulu8.76.0.17-ca-jdk8.0.402-macosx_aarch64/zulu-8.jdk/Contents/Home/jre) VULNERABLE (HTTP 200) https://dv-g3b-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://dv-g3c-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ov-g3b-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ov-g3c-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ev-g3b-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ev-g3c-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://dv-g3b-aaa-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://dv-g3c-aaa-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ov-g3b-aaa-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ov-g3c-aaa-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ev-g3b-aaa-emudhra.we-have-a-problem.com/ VULNERABLE (HTTP 200) https://ev-g3c-aaa-emudhra.we-have-a-problem.com/ [error] java.lang.RuntimeException: compromised CAs are in use, or we encountered a network error [error] at scala.sys.package$.error(package.scala:27) [error] at CheckCompromisedCa$.test(CheckCompromisedCa.scala:36) [error] at CheckCompromisedCa$.main(CheckCompro

## Scala 3.10 released!

DevFeed: [Scala 3.10 released!](<https://devfeed.tech/articles/scala-3-10-released-85231.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.10/>)

Published: 2026-10-11T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [toolchain](<https://devfeed.tech/topics/toolchain.md>)

Tags: [announce](<https://devfeed.tech/tags/announce.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [cross-compilation](<https://devfeed.tech/tags/cross-compilation.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

Scala 3.10.0 is the first release in the Scala Next series. It stabilizes SIP-67, moves three SIPs to preview, removes deprecated syntax while preserving binary compatibility, and introduces compiler, standard library, tooling, and distribution changes. The release notes recommend Scala 3.9 LTS for projects seeking the longest support window.

### Source excerpt

Scala 3.10 released! We are happy to announce Scala 3.10.0, the first release of the new Scala Next series. This release stabilizes SIP-67, moves three SIPs into preview, and starts dropping legacy language features that have been deprecated for several minor releases. Scala 3.3 LTS and Scala 3.9 LTS put compatibility with Scala 2.13 first. Now, nearly five years after Scala 3.0, Scala 3.10 starts removing legacy syntax and features that have been deprecated for several minor releases. The standard library also starts using more Scala 3 features, such as inline and extension methods. Binary compatibility is preserved: libraries compiled with earlier Scala 3 versions keep working, including those that used features now removed. Source that still uses those features must be updated to compile with 3.10. Macros and compiler plugins may need to be adapted to changed internal representations (details below). If you publish a library and want the longest support window, Scala 3.9 LTS remains the recommended version to build against. Cross-compilation between Scala 2 and 3.10 is no longer supported because of the removed legacy features. Some libraries might remain cross-compilable, but it is expected that cross-compiled libraries will remain on Scala 3.9 LTS indefinitely. Before checking a 3.10 artifact with MiMa, upgrade to MiMa 1.2.1 or later: that release adds Scala 3.9 and 3.10 support and fixes several false positives. Highlights SIP-67: pattern matching under strictEquality no longer needs CanEqual - now stable. (But strict equality remains an opt-in feature.) Three SIPs move to preview behind -preview: @unroll, relaxed lambda syntax, and referenceable package objects. Deprecated syntax previously retained for compatibility with Scala 2, such as A with B, is now an error; see Breaking changes. The compiler reports Recursion limit exceeded instead of crashing with a StackOverflowError (details). Scala is now also distributed as .deb and .rpm packages. Breaking change

## VirtusLab assumes responsibility for Scala 2 maintenance

DevFeed: [VirtusLab assumes responsibility for Scala 2 maintenance](<https://devfeed.tech/articles/virtuslab-assumes-responsibility-for-scala-2-maintenance-66638.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/scala2-maintenance.html>)

Published: 2026-10-06T22:00:00Z

Content type: news

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [maintenance](<https://devfeed.tech/tags/maintenance.md>), [migration](<https://devfeed.tech/tags/migration.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

VirtusLab has assumed responsibility for maintaining Scala 2 in coordination with the Scala Center and Scala Core Team, which also manage Scala 3 development. It plans to maintain Scala 2.12 and 2.13 as long as necessary and continue improving migration to Scala 3. The next releases are being planned and discussed in the Scala Contributors forum.

### Source excerpt

We are happy to announce that VirtusLab has assumed responsibility for maintenance of Scala 2. This means that VirtusLab, in coordination with the Scala Center and the Scala Core Team, now manages the development of both Scala 2 and Scala 3. Former members of the Scala 2 team at Akka have joined the VirtusLab OSS team, so there will be no impact on Scala 2 maintenance or Scala 2's future. Our plans for Scala 2 maintenance have long been documented at https://www.scala-lang.org/development/#scala-2-maintenance and the wordings there have not changed. VirtusLab will maintain Scala 2.12 and 2.13 as long as necessary and will also continue to improve the Scala 2-to-3 migration story. Lukas Rytz remains on the Scala Core Team but as Scala 2 Representative, no longer as Akka Representative. We are deeply grateful to Akka for their years of support for Scala and its governance and ecosystem. If you have any questions, see https://scala-lang.org/community/ for ways to contact us. The next Scala 2.12 and 2.13 releases are being planned and discussed on these threads on the Scala Contributors forum: Scala 2.12.22: https://contributors.scala-lang.org/t/scala-2-12-22-release-planning/7309 Scala 2.13.19: https://contributors.scala-lang.org/t/scala-2-13-19-release-planning/7293

## Scala Days 2026 and October Scala Community Events

DevFeed: [Scala Days 2026 and October Scala Community Events](<https://devfeed.tech/articles/let-s-meet-in-october-65425.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/10/06/lets-meet-in-october.html>)

Published: 2026-10-05T22:00:00Z

Content type: news

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>)

Tags: [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [berlin](<https://devfeed.tech/tags/berlin.md>), [conference](<https://devfeed.tech/tags/conference.md>), [conferences](<https://devfeed.tech/tags/conferences.md>), [days](<https://devfeed.tech/tags/days.md>), [developers](<https://devfeed.tech/tags/developers.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [online](<https://devfeed.tech/tags/online.md>), [programming](<https://devfeed.tech/tags/programming.md>)

### AI overview

Scala Days 2026 will take place in Berlin on October 12-13, with workshops on October 14-15 and a EUR 15 livestream option. The article also lists Scala and functional programming events in several cities throughout October.

### Source excerpt

Scala Days 2026 is just around the corner! Next week, on 12 and 13 October, the Scala community will come together at Kulturbrauerei in Berlin for two days of learning, sharing experiences, and catching up with friends and colleagues. The program opens with a keynote by Martin Odersky. There will also be interactive labs, giving you time to explore tools and ideas with their maintainers. Whether you use Scala every day or are getting to know the ecosystem, we look forward to welcoming you. If you'd like to stay a little longer, two-day workshops follow on 14 and 15 October at Hotel Oderberger, with practical sessions on AI-assisted development and Safe Scala. Workshops require a separate ticket or a conference and workshop bundle. There are also satellite events around the conference: a guided tech walk and dinner hosted by VirtusLab on 11 October, and Typelevel Traverses Berlin (waitlist) on 14 October, hosted at Zalando. Both offer more time to meet fellow Scala developers and exchange ideas. Buy your Scala Days ticket and join us in Berlin. Join us online, or meet your local community If you can't travel to Berlin, you can still follow the conference from home. Buy a streaming ticket by choosing Livestream Access in the ticket shop. Tickets cost EUR 15 and provide access to the live conference sessions. Workshops and interactive labs are not included in the stream. You can find more details in the online attendance announcement. There are also plenty of opportunities to meet fellow Scala developers closer to home this October. Local meetups and conferences are a lovely way to exchange ideas, learn from each other, and get to know the people behind the projects you use. Scala events this October Here are some upcoming events around the Scala and functional programming communities, in date order: 7 October, London, UK: London Scala Talks, with talks on Scala 3 specialization, probability and Balatro, and suspendable query DAGs. 8 October, Prague, Czechia: Functional J

## sbt 2.1.0 Beta: Rebuilding the sbt Plugin Ecosystem

DevFeed: [sbt 2.1.0 Beta: Rebuilding the sbt Plugin Ecosystem](<https://devfeed.tech/articles/reforesting-the-sbt-plugin-ecosystem-and-sbt-2-1-0-beta-55203.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/09/16/sbt-plugin-updates.html>)

Published: 2026-09-15T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [beta](<https://devfeed.tech/tags/beta.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [github](<https://devfeed.tech/tags/github.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [migration](<https://devfeed.tech/tags/migration.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [scala](<https://devfeed.tech/tags/scala.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

The Scala Center describes work to support the sbt 2.x plugin ecosystem, including migration tooling, ABI stabilization, compatibility support, and plugin updates. As of September 2026, Scaladex lists 172 plugins available for sbt 2.x.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. Plugin as an ecosystem Out of the box, sbt handles basic functionality like building and testing Scala code. Once you get used to the basics, the build can be extended further by using community plugins. Plugins range from simple utilities to support for new programming languages. One aspect of a plugin project is that it can be created and developed without waiting for a release of sbt, so it's a great way to try new ideas or collaborate across the community. If you want to discover plugins two sources are: Community Plugins page Scaladex Preparing for reforestation Since the ecosystem is an essential element of the user experience, the health of the plugin ecosystem is always our concern. This is especially so when we release a new major version, which burns the old forest. All plugins need to be cross built, and re-published, like new saplings springing from the ash. There are several strategies we adopted to aid the reforestation. Over the years, we have centralized major plugins to GitHub sbt organization. This lets us add new maintainers to the plugin who can review the PRs. Created the sbt 2.x plugin migration wiki page to coordinate the migration effort. We locked down the ABI for 2.x with 2.0.0-RC1, which was released in August 2025. This gave a head start for the plugin authors to cross publish before sbt 2.0 came out. In March 2026, Anatolii Kmetiuk (Scala Center) created sbt2-compat plugin, which adds a compatibility layer so that the same plugin can target both sbt 1 and sbt 2. Beyond tooling, we've actively sent pull requests to migrate the plugins. I'm happy to report that as of this writing (September 2026), Scaladex lists 172 plugins available for sbt 2.x. Many thanks for the community effort by volunteers like Kenji Yoshida and many others. In this post, I'd like to highlight some of the mo

## Scala 3.9 LTS released!

DevFeed: [Scala 3.9 LTS released!](<https://devfeed.tech/articles/scala-3-9-lts-released-43575.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.9/>)

Published: 2026-09-02T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [version](<https://devfeed.tech/topics/version.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [maintenance](<https://devfeed.tech/topics/maintenance.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [compiler](<https://devfeed.tech/tags/compiler.md>), [lts](<https://devfeed.tech/tags/lts.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

Scala 3.9.0 opens a new Long Term Support line, succeeding Scala 3.3 LTS as the recommended baseline for library authors and conservative production users. The announcement explains the LTS and Scala Next release models, compatibility considerations, backports, and the continued maintenance of Scala 3.3 LTS.

### Source excerpt

Scala 3.9 LTS released! We are happy to announce Scala 3.9.0, opening the new Long Term Support line for Scala 3. It succeeds Scala 3.3 LTS as the recommended baseline for library authors and conservative production users, while keeping the Scala Next line available for teams that want the latest language work as soon as it is released. What does LTS mean? Scala 3 follows the Scala LTS and Scala Next model. Scala Next receives regular minor releases with new language features, tooling work, and ecosystem changes. Scala LTS receives patch releases focused on bug fixes, diagnostics, tooling improvements, and carefully selected quality-of-life changes that are also subject to the compatibility guarantees of the LTS line. Libraries published with Scala 3.9 LTS can be consumed by later 3.9 patch releases and by Scala Next. The 3.9 line is expected to receive patches and backports for an extended period. Library maintainers: artifacts built with Scala 3.9 cannot be consumed by Scala 3.3 projects, so treat the move from Scala 3.3 LTS to Scala 3.9 LTS as a minor-version publishing decision for your own libraries. Looking back at Scala 3.3 LTS Scala 3.3.0 was released in May 2023 and became the first Scala 3 LTS. It carried the ecosystem through more than three years of Scala 3 development while Scala Next delivered new syntax, new standard-library work, new tooling integration, and deeper compatibility testing. The 3.3 LTS line was not a frozen branch. As I write this, 1,420 of 2,380 pull requests merged into the main Scala 3 compiler branch since 3.4.0 were also backported to Scala 3.3 LTS. That's almost 43% of all changes! That work kept 3.3 useful as a publishing target while still protecting the compatibility expectations that made it attractive in the first place. The result of this decision is visible in the ecosystem - roughly 56% of Scala 3 libraries are currently published using Scala 3.3 LTS. What's more, the next patch release - Scala 3.3.9 - is planned within th

## Fixing a remote execution vulnerability in sbt

DevFeed: [Fixing a remote execution vulnerability in sbt](<https://devfeed.tech/articles/fixing-a-remote-execution-vulnerability-in-sbt-43569.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/08/10/sbt-remote-tcp-advisory.html>)

Published: 2026-08-09T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Security](<https://devfeed.tech/topics/security.md>), [bug](<https://devfeed.tech/topics/bug.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [Scala](<https://devfeed.tech/topics/scala.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [bug](<https://devfeed.tech/tags/bug.md>), [execution](<https://devfeed.tech/tags/execution.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [rpc](<https://devfeed.tech/tags/rpc.md>), [scala](<https://devfeed.tech/tags/scala.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The post describes a vulnerability in sbt that enables remote code execution when TCP server communication is enabled. It explains the access-control issue, affected sbt versions, and recommends removing the TCP setting or upgrading to sbt 1.12.15 or 2.0.6 and later.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. TL;DR Only builds that explicitly set serverConnectionType are affected. You can remove the setting from your build, or upgrade to sbt 1.12.15 / sbt 2.0.6 or later by putting the following in project/build.properties: sbt.version=1.12.15 Note that installing a new sbt command does not affect the sbt version used by each individual build. The vulnerability As part of our ongoing work on the sbt 2 release, we've been reviewing bug reports and pull requests. Recently we received a security report GHSA-m2pw-22cj-jq4v from Arpit Jain that an attacker is able to execute arbitrary code remotely via the sbt server when the serverConnectionType is set to ConnectionType.Tcp. By default, sbt uses UNIX domain sockets on Linux and macOS, and named pipes on Windows, but this can be changed to TCP using the following setting: Global / serverConnectionType := ConnectionType.Tcp This will use a TCP port that can be calculated deterministically from the working directory, e.g. 5001, for the sbt server communication. An attacker can then craft a JSON-RPC message, masquerading as an sbt client. In a normal sequence, using TCP would go through a token authentication so only the local user can use the sbt server; however, there were several endpoints that were not protected by the access control, which allowed improper escalation. This is a form of CWE-425: Direct Request. The vulnerability has existed since sbt 1.1.0 and affects both the sbt 1.x and sbt 2.x series. The fix The primary fix was to make sure all LSP-like endpoints are protected behind authorization when using TCP. The fix is available in sbt 1.12.15 and 2.0.6. The remediation was implemented by Eugene and Anatolii using GitHub's private fork feature. The full advisory is available as GHSA-m2pw-22cj-jq4v. We recommend removing the serverConnectionType setting from y

## Using generative AI and human review to improve Scala API documentation

DevFeed: [Using generative AI and human review to improve Scala API documentation](<https://devfeed.tech/articles/coaxing-quality-output-from-generative-ai-43568.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/07/06/quality-from-genai.html>)

Author: About the author

Published: 2026-07-05T22:00:00Z

Content type: opinion

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Generative AI](<https://devfeed.tech/topics/generative-ai.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [iteration](<https://devfeed.tech/topics/iteration.md>), [Code](<https://devfeed.tech/topics/code.md>), [Prompt Engineering](<https://devfeed.tech/topics/prompt-engineering.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [code](<https://devfeed.tech/tags/code.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [human-review](<https://devfeed.tech/tags/human-review.md>), [iteration](<https://devfeed.tech/tags/iteration.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-as-a-judge](<https://devfeed.tech/tags/llm-as-a-judge.md>), [prompting](<https://devfeed.tech/tags/prompting.md>), [scala](<https://devfeed.tech/tags/scala.md>)

### AI overview

This report describes an approach to improving Scala standard-library API documentation with generative AI. It addresses output quality and human review capacity through iteration, LLM-based judging, deterministic code, orchestration harnesses, and scripts.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment. The work is coordinated by the Scala Center. The work described in this post was done by Bill Venners and Chua Chee Seng of Artima. One of the tasks funded under the STA project is to improve Scala's API documentation. Such a task looks like a natural fit for generative AI, because the work is repetitive and the code to document is nearby in the source. But handing the work to an AI raises two challenges. The first is quality: an AI model will readily produce documentation, but it may be mediocre or wrong. The second challenge is managing human review time: someone will have to check all that output. This post is a report on how we approached these problems when using AI to improve API documention of Scala's standard library: what we tried and how it worked out. Quality writing requires iteration. You write a draft, review it (or have someone else review it), then improve it. You repeat this process until you're happy with the quality. One way to achieve quality with generative AI, therefore, is to delegate the writing part to the AI model and review it yourself, but this doesn't scale. An AI model can generate content at a much greater rate than you can review it. Because of this, we decided to use the "LLM as a judge" technique in an attempt to raise the quality of the output as high as possible prior to asking humans to review it. Another way we tried to raise the quality of the AI output prior to human review is to use harnesses to orchestrate the AI work. First, we wrote a todo-writer application that reformatted doc comments for consistency and inserted text markers in the standard library source to precisely indicate where we wanted an AI to insert focused documentation. Then we created a script to drive the filling-in process. Finally, we attempted to keep the review tasks for humans to a reasonable size. The rest of this post describes five techniques that formed our overall approach. Tech

## sbt 2 is now available!

DevFeed: [sbt 2 is now available!](<https://devfeed.tech/articles/sbt-2-is-now-available-43567.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/06/29/sbt2.html>)

Published: 2026-06-28T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [migration](<https://devfeed.tech/topics/migration.md>), [test](<https://devfeed.tech/topics/test.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [client](<https://devfeed.tech/topics/client.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2025](<https://devfeed.tech/tags/2025.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [development](<https://devfeed.tech/tags/development.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [migration](<https://devfeed.tech/tags/migration.md>), [release](<https://devfeed.tech/tags/release.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

The Scala community has released sbt 2 after five years of development. The new build tool version uses Scala 3.8.4 and requires JDK 17, adds a native-image client, incremental testing, Bazel-compatible local and remote caching, project matrices, client-side commands, and updated documentation.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. After five years of development, sbt 2 is out. Since the experimental sudori part 1 blog post in 2021, more than 82 people have contributed to the project. We would like to thank community and corporate contributors, Scala Center, and Sovereign Tech Fund for their support. What's new in sbt 2? sbt 2 is a new version of sbt. If you're familiar with sbt 1.x, hopefully the jump is not too far, but we have pushed sbt to the modern standard. The headline features are: sbt 2.x uses Scala 3.8.4 for build definitions and plugins (Both sbt 1.x and 2.x are capable of building Scala 2.x and 3.x), which requires minimum JDK 17 Uses sbtn (native-image client) for faster startup. test changed to incremental test. Local/remote cache system that is Bazel-compatible. compile and test are both rewritten to be cachable tasks. Project matrix, which was available via plugin in sbt 1.x, is in-sourced in sbt 2.x. Client-side run. Client-side console. New documentation. For more details, please check out sbt 2.0 changes summary and the Scala Days 2025 talk sbt 2.0: go big from 2025. How do I get started with sbt 2? The sbt version used for your build is upgraded by putting the following in project/build.properties: sbt.version=2.0.1 This mechanism allows that sbt 2.0.1 is used only for the builds that you want. Download the official sbt runner from SDKMAN, or download from https://github.com/sbt/sbt/releases/tag/v2.0.1 to upgrade the sbt shell script, sbtn, and the launcher. Repopulating the plugin ecosystem Major plugins are already available on sbt 2.x. Under the sbt 2 workstream, Anatolii from Scala Center has created the sbt2-compat plugin, which bridges the source-level differences between sbt 1.x and 2.x. This allows cross-building of a plugin, aiding the migration process. Also under the STA workstream, Rikito Taniguchi from

## Scala 3.3.8 LTS is now available!

DevFeed: [Scala 3.3.8 LTS is now available!](<https://devfeed.tech/articles/scala-3-3-8-lts-is-now-available-43571.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.3.8/>)

Published: 2026-06-09T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [releases](<https://devfeed.tech/topics/releases.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>)

Tags: [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [lts](<https://devfeed.tech/tags/lts.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Scala 3.3.8 LTS is a patch release that backports bug fixes and improvements from the Scala Next series. The release adds JDK 26 support, improves coverage support, introduces the @uncheckedOverride annotation, updates REPL Ctrl-C handling, and includes linting, presentation compiler, and lazy val implementation improvements. The changes were tested for binary and source compatibility across more than 1,500 projects.

### Source excerpt

Scala 3.3.8 LTS is now available! This patch release backports most of the bugfixes and some of the improvements introduced in the Scala Next series to the Scala 3.8.4 release. All of the backported changes were proven to not break either binary or source compatibility, by testing over 1500 projects in the Scala 3 Open Community Build. Notable changes Support for JDK 26 #24430 Multiple coverage improvement to make it on par with Scala 2 support including // $COVERAGE-OFF$ and // $COVERAGE-ON$ markers New @uncheckedOverride annotation for definitions that may override. #24545 Trap Ctrl-C in the REPL: if no command is running clear the prompt, if some command is running ask for confirmation before exiting. #24127 Numerous linting and presentation compiler improvements and fixes. New -Yfuture-lazy-vals options that allows to compile with new lazy val implementation compatible with all JDK 9+ #637 For a full list of changes and contributor credits, please refer to the release notes. Scala LTS Release Notice The next planned LTS 3.3 release will include updates introduced until last Scala 3.9.x before 3.10. Scala 3.9.x will also be a new LTS release. We'll continue to backport bug fixes and improvements from the Scala Next series to the 3.3.x series for the next year after the release 3.9.0.

## Improving Scala's docs and website

DevFeed: [Improving Scala's docs and website](<https://devfeed.tech/articles/improving-scala-s-docs-and-website-43566.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/06/09/sovereign-doc-project.html>)

Published: 2026-06-08T22:00:00Z

Content type: article

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [Website](<https://devfeed.tech/topics/website.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [API](<https://devfeed.tech/topics/api.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [api-documentation](<https://devfeed.tech/tags/api-documentation.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [scala](<https://devfeed.tech/tags/scala.md>), [standard-library](<https://devfeed.tech/tags/standard-library.md>), [tools](<https://devfeed.tech/tags/tools.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

The Scala Center is coordinating a Sovereign Tech Fund-supported project to improve outdated, incomplete, poor-quality, or missing documentation for Scala. The work focuses primarily on Scala 3 Scaladoc and the Scala website, with some important Scala 2 improvements also included.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment. The work is coordinated by the Scala Center. We have collected possible documentation tasks from three sources: Tasks in the original proposal we made to the Sovereign Tech Agency Tasks collected in internal discussions since then Tasks from community suggestions on this Contributors forum thread This blog post summarizes what we have collected, identifies tasks that we have chosen to tackle, and describes work that is already underway. Project goals We aim to identify documentation, both API documentation (Scaladoc) and the docs on the Scala website, that is: Outdated, or Incomplete or poor quality, or Missing entirely And we want to address those shortcomings, to aid both: New users coming to Scala Existing users of Scala Project scope A major focus will be on the Scaladoc for the standard library. We will update and expand it. Along the way, if we find that limitations of the Scala 3 Scaladoc tool are causing quality issues in the doc, improving the tool is in scope. The project scope also includes the documentation on our website such as the Scala language specification, getting-started docs, language tour, features guides, Scala Toolkit documentation, and so forth. Scala 3 is the primary focus, but we can also make especially important improvements on the Scala 2 side. What's not in scope? Third-party tools, libraries, and publications are not in scope. That said, it is sometimes appropriate for our website and docs to describe and link to third-party documentation and resources. Examples of such documentation that is in scope for improvement include: the Scala community page, the Scala IDEs page, the Scala Toolkit documentation (because the Toolkit includes third-party libraries), and the Scala books page. What did we initially propose? In the Center's original proposal we identified the following areas or "work packages". Any work we do must fit in at least one of these areas, and we must do

## Scala 3.8.4 is now available!

DevFeed: [Scala 3.8.4 is now available!](<https://devfeed.tech/articles/scala-3-8-4-is-now-available-43574.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.8.4/>)

Published: 2026-06-04T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [parsing](<https://devfeed.tech/tags/parsing.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Scala 3.8.4 is a release focused on security audit fixes, including hardened TASTy parsing, a stored XSS fix in Scaladoc, improved process-parser error handling, and a JAR-walking fix. It also expands compiler-setting help and upgrades the bundled Scala CLI to 1.14.0.

### Source excerpt

Release highlights Security audit fixes Scala 3.8.4 includes improvements and fixes for issues discovered during the Scala codebase security audit carried out in collaboration with the Open Source Technology Improvement Fund and Quarkslab. Notable fixes in this release include: Hardened TASTy parsing to prevent infinite loops on maliciously crafted files (#25676) Fixed a stored XSS vulnerability in Scaladoc (#25681) Improved error handling in scala.sys.process.Parser.tokenize (#25675) Fixed TastyPrinter's JAR-walking logic to include subdirectories (#25678) :help syntax for all compiler settings (#26052) You can now append :help to any compiler setting to see its documentation -- not just a fixed subset as before. This works wherever you pass compiler options, making it easier to discover available flags without leaving your workflow. With the Scala runner, add :help to a flag on the command line when running a script or project: > scala test.scala -Xkind-projector:help -Xkind-projector Allow `*` as type lambda placeholder to be compatible with kind projector. When invoked as -Xkind-projector:underscores will repurpose `_` to be a type parameter placeholder, this will disable usage of underscore as a wildcard. Default disable Choices: disable, , underscores In the REPL, pass the same flag through :settings: scala> :settings -Wunused:help -Wunused Enable or disable specific `unused` warnings Choices: - nowarn, - all, - imports : Warn if an import selector is not referenced., - privates : Warn if a private member is unused, - locals : Warn if a local definition is unused, - explicits : Warn if an explicit parameter is unused, - implicits : Warn if an implicit parameter is unused, - params : Enable -Wunused:explicits,implicits, - patvars : Warn if a variable bound in a pattern is unused, - linted : Enable -Wunused:imports,privates,locals,implicits Upgrade to Scala CLI 1.14.0 The bundled Scala CLI has been upgraded from 1.11.x through 1.12.5, 1.13.0, to 1.14.0. Notable a

## Scala Codebase Security Audit Complete

DevFeed: [Scala Codebase Security Audit Complete](<https://devfeed.tech/articles/scala-codebase-security-audit-complete-43565.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/06/01/first-part-security-audit.html>)

Published: 2026-05-31T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Security](<https://devfeed.tech/topics/security.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [audit](<https://devfeed.tech/topics/audit.md>), [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [library](<https://devfeed.tech/tags/library.md>), [lts](<https://devfeed.tech/tags/lts.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

The Scala Center reports the first results of a security audit covering the Scala 3 compiler and standard library. The audit found five medium-severity issues, one low-severity issue, and two informational findings; all were addressed in the Scala 3.3 LTS and 3.8 branches. Most findings affected scenarios where the compiler processes untrusted input as a service.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: Maintenance of the Standard Library/Core Library Modules and APIs. The work is coordinated by the Scala Center. The Scala Center is proud to share the first results of the security audit of Scala carried out in collaboration with Open Source Technology Improvement Fund and the security researchers at Quarkslab. The audit was divided into two major parts: an assessment of the Scala 3 compiler and Scala standard library codebases, and a separate review of Scala's supply-chain security. This first publication focuses on the compiler and standard library audit. Since many reported security issues in Scala ecosystems involve the standard library, the audit aimed to strengthen the security and robustness of Scala's core components through a combination of manual code review and automated tooling, including fuzzing and Java deserialization gadget finders. Results Read the full report here. No critical or major security issues were identified during the audit. However, the review uncovered 5 medium severity issues, 1 low severity issue, and 2 informational findings, all of which have since been addressed by the Scala maintainers. All of these issues are fixed as of the date of this blog post, both for the 3.3 LTS branch and for the main 3.8 branch. Importantly, these issues do not affect typical users compiling Scala code locally or through continuous integration pipelines. Most findings were only relevant in scenarios where the Scala compiler is exposed as a service and processes untrusted input, where they could potentially lead to denial-of-service-type behavior. Fixes All reported issues were present in 3.8-RC1 and fixed before the publication of this blog post, both in the Scala 3.3 LTS branch and in the main Scala 3.8 development branch. One example was a medium severity issue in the compiler's handling of TASTy files. The compiler did not validate that certain offsets were nonnegative, whic

## Scala Days 2026: Call for proposals open

DevFeed: [Scala Days 2026: Call for proposals open](<https://devfeed.tech/articles/scala-days-2026-call-for-proposals-open-43564.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/04/30/scala-days-2026-cfp.html>)

Published: 2026-04-29T22:00:00Z

Content type: news

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [conference](<https://devfeed.tech/tags/conference.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [scala](<https://devfeed.tech/tags/scala.md>)

### AI overview

Scala Days 2026 has opened its call for proposals for talks, interactive labs, and workshops. Submissions should share practical insights, real-world experience, technical deep-dives, or forward-looking ideas related to Scala and its ecosystem.

### Source excerpt

Scala Days 2026: Call for proposals open Submit your talk https://cfp.scaladays.org/scala26/cfp and be part of Scala Days 2026! The Call for Proposals is now open and will close on May 31, 2026, at 23:59 CEST. The Program Committee is looking for talks, labs, and workshops that showcase how Scala is evolving and delivering value in today's fast-changing technology landscape. In particular, we're excited to hear practical insights, real-world experience reports, and forward-looking ideas. See the topics below for inspiration. Kind reminder: Super Early Bird tickets are available only until the end of the day on April 30, 2026. Formats This year's program includes three submission formats. Talks and Interactive labs are part of the main conference program, while Workshops take place after the conference and require a separate ticket. Talks (30 minutes) Classic conference talks for sharing ideas, lessons learned, technical deep-dives, and real-world experience. We're looking for talks that bring real value to the community: practical insights, innovative approaches, hard-earned lessons, or fresh perspectives on Scala and its ecosystem. We will select up to 48 talks, organized across 3 parallel tracks as part of the main conference program. Interactive Labs (2 hours) Interactive labs are a new format at Scala Days 2026: small-group, highly interactive sessions built around live demos, guided exploration, and practical experimentation during the conference. This format is ideal for showcasing tools, libraries, frameworks, and new ideas in action. The goal is for participants to explore, experiment, and leave with practical experience they can immediately apply. Because sessions are limited to 2 hours total, proposals should be designed to get participants engaged quickly, with minimal setup time and a clear path into the core experience. Interactive labs are also a great fit for open-source maintainers who want to introduce their projects, onboard new users, and grow the

## sbt 2 Development Progress, Features, and Plugin Ecosystem Migration

DevFeed: [sbt 2 Development Progress, Features, and Plugin Ecosystem Migration](<https://devfeed.tech/articles/last-mile-towards-sbt-2-43563.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/04/14/last-mile-towards-sbt2.html>)

Published: 2026-04-13T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [Parallelism](<https://devfeed.tech/topics/parallelism.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [test](<https://devfeed.tech/topics/test.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [go](<https://devfeed.tech/tags/go.md>), [porting](<https://devfeed.tech/tags/porting.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [scala](<https://devfeed.tech/tags/scala.md>)

### AI overview

The post reports on sbt 2 development toward a stable release. It describes Scala 3 build definitions and plugins, simpler build settings, incremental testing, Bazel-compatible caching, faster startup through sbtn, and parallel project-matrix builds. It also covers beta releases, plugin porting, compatibility work, tooling support, and documentation.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. At conferences or on social media, the question we get most often is: When is sbt 2 coming out? We'll discuss the plan in this post. But let's go over the status first. What's new in sbt 2? sbt 2 is a new major version of sbt. If you're familiar with sbt 1.x, hopefully the jump is not too far, but we have pushed sbt to a more modern standard. The headline features are: sbt 2.x uses Scala 3.x (rather than Scala 2.12) for build definitions and plugins (Both sbt 1.x and 2.x are capable of building Scala 2.x and 3.x) Embraces a simpler build.sbt via common settings test changed to an incremental test Local and remote cache system that is Bazel-compatible Uses sbtn (native-image client) for faster startup Project matrix that can cross build subprojects in parallel For more details, please check out the Scala Days 2025 talk sbt 2.0: go big that I gave in August 2025. To share the progress thus far, we released the sbt 2.0 ideas post in 2023, with sbt 2.0.0-alpha7. After a few more years of development, we released a beta version sbt 2.0.0-RC2 that's ready for testing, around Scala Days 2025. Since then, we have been releasing more beta versions with both bug fixes and community-contributed feature enhancements. Perhaps surprising to some, sbt 2.x already started the binary compatibility from the RC series. This gave us a head start on repopulating the plugin ecosystem. Repopulating the plugin ecosystem Thanks to the community effort, we already have 60+ plugins ported to sbt 2.x. This is amazing for a build tool that hasn't been released yet. Special thanks to Kenji Yoshida for pull requests, preparing and porting many plugins to sbt 2. Under the sbt 2 workstream, Anatolii from Scala Center has created the sbt2-compat plugin, which bridges the source-level differences between sbt 1.x and 2.x. This allows cross-bui

## Fixing a Command Injection Vulnerability in sbt

DevFeed: [Fixing a Command Injection Vulnerability in sbt](<https://devfeed.tech/articles/fixing-a-command-injection-vulnerability-in-sbt-43562.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/03/31/sbt-security-advisory.html>)

Published: 2026-03-30T22:00:00Z

Content type: article

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [Shell](<https://devfeed.tech/topics/shell.md>), [Git](<https://devfeed.tech/topics/git.md>), [Scala](<https://devfeed.tech/topics/scala.md>)

Tags: [core](<https://devfeed.tech/tags/core.md>), [cve](<https://devfeed.tech/tags/cve.md>), [release](<https://devfeed.tech/tags/release.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

The Scala Center reports and fixes a command injection vulnerability in sbt's Windows handling of source dependencies. The issue, CVE-2026-32948, affects sbt versions before 1.12.8 and sbt 2.0.0 release candidates before RC10; users should update.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. As part of our ongoing work on the sbt 2 release, we've been reviewing and hardening core parts of the sbt codebase. During that work, we discovered a command injection vulnerability in how sbt resolves source dependencies on Windows. The issue has been assigned CVE-2026-32948, rated Moderate (CVSS 6.7), and is now fixed. If you use sbt on Windows, update to sbt 1.12.8 or sbt 2.0.0-RC10 or later to apply the fix. The vulnerability sbt has the source dependencies feature that lets you depend on a VCS repository in your build definition. For example, to depend on the develop branch of a project published to GitHub: lazy val dep = RootProject( uri("https://github.com/sbt/io.git#develop") ) When sbt resolves this, it clones the repository and checks out the branch specified in the URI fragment - the part after #. To do this, sbt runs a VCS client (git, hg, or svn) as an external process. On Windows, sbt historically wrapped these VCS commands in cmd /c - routing them through the Windows command interpreter. cmd.exe treats characters like &, |, and ; as command separators. The URI fragment is user-controlled and was passed to VCS commands without any validation. This allows an attacker to break out of the intended git command and execute an arbitrary shell command on Windows. For example, consider a dependency declared as: lazy val vulnerable = RootProject( uri("https://github.com/sbt/io.git#develop%26%26calc.exe") ) The %26%26 decodes to &&. When this reaches cmd /c git checkout develop&&calc.exe, the command interpreter executes two commands: first git checkout develop, then calc.exe, starting the Windows Calculator. This is a classic OS command injection (CWE-78). The vulnerability has existed since sbt 0.9.5 and affects both the sbt 1.x line and sbt 2.0 release candidates on Windows. Severity The severity is

## Scala 3.8.3 is now available!

DevFeed: [Scala 3.8.3 is now available!](<https://devfeed.tech/articles/scala-3-8-3-is-now-available-43573.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.8.3/>)

Published: 2026-03-30T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [performance](<https://devfeed.tech/tags/performance.md>), [programming](<https://devfeed.tech/tags/programming.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

Scala 3.8.3 is available with local coverage exclusions, an experimental safe mode for capability-safe and untrusted code, and the Scala 2 JVM backend optimizer ported to Scala 3.

### Source excerpt

Scala 3.8.3 is now available! Release highlights Local coverage exclusions with // $COVERAGE-OFF$ blocks (#24486) Coverage-instrumented builds can now disable coverage for a selected region of code, instead of excluding a whole file or class. This is useful for generated code, intentionally defensive branches, or support code that would otherwise distort coverage results. //> using scala 3.8.3 //> using options --coverage-out coverage-data class Parser: def parse(input: String): Int = input.toInt // $COVERAGE-OFF$ def debugFallback(input: String): Int = if input == "zero" then 0 else -1 // $COVERAGE-ON$ @main def CoverageTest = { val parser = Parser() assert(parser.parse("42") == 42) } Only the code between the markers is skipped by coverage instrumentation. The rest of the file is still measured as usual. Safe mode for capability-safe code (#25307) Scala 3.8.3 introduces safe mode, a new experimental language subset that can be enabled with import language.experimental.safe or -language:experimental.safe. As described in the safe mode reference, this is not just "stricter capture checking": it is a capability-safe subset intended for agent-generated or otherwise untrusted code. The underlying model is also described in the research paper Tracking Capabilities for Safer Agents, which proposes using Scala 3 with capture checking as a programming-language-based safety harness for AI agents. When safe mode is enabled, the compiler rejects unchecked casts and unchecked pattern matches, forbids escape hatches such as caps.unsafe, @unchecked, and runtime reflection, turns on capture checking with mutation tracking, and restricts access to global APIs unless they are known-safe or explicitly reviewed. That last point is what makes the feature practical. Safe code is meant to call a restricted set of APIs directly, while effectful or implementation-dependent behavior can still be exposed through wrappers marked @assumeSafe. The implementation in #25307 makes that boundary e

## Announcing Scala Days 2026

DevFeed: [Announcing Scala Days 2026](<https://devfeed.tech/articles/announcing-scala-days-2026-43561.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/03/26/scala-days-2026.html>)

Published: 2026-03-25T23:00:00Z

Content type: news

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [announce](<https://devfeed.tech/tags/announce.md>), [berlin](<https://devfeed.tech/tags/berlin.md>), [conference](<https://devfeed.tech/tags/conference.md>), [events](<https://devfeed.tech/tags/events.md>), [foss](<https://devfeed.tech/tags/foss.md>), [germany](<https://devfeed.tech/tags/germany.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [scala](<https://devfeed.tech/tags/scala.md>)

### AI overview

Scala Days 2026 will take place in Berlin on October 12-13, followed by workshops and other community events on October 14-15. The Scala Center is partnering with Plain Schwarz to organize the conference, with early-bird tickets available and talk and workshop proposals opening in late April.

### Source excerpt

We are very happy to announce that the Scala Days 2026 conference will be taking place 12 - 13 October in Berlin, Germany, one of Europe's most vibrant tech and open source hubs, known for its strong culture of collaboration and its growing role in advancing digital sovereignty through open technologies. Grab your Super Early Bird ticket and join us in Berlin this autumn! Co-located events Workshops will follow on 14-15 October, with various community-driven, co-located events taking place around the conference, possibly including the preceding weekend. Meet Plain Schwarz For the Scala Days 2026 conference, the Scala Center partnered with Berlin-based company Plain Schwarz, internationally renowned for organising conferences like Berlin Buzzwords and FOSS Backstage. Join us in welcoming Paul and the Plain Schwarz team to the Scala Days community as we work together on a refreshed and dynamic 2026 edition that stays true to Scala Days' core spirit: business-driven and community-infused. Call to action Get your tickets at Super Early Bird price until April 9th, 23:55 CEST. Interested in sponsoring Scala Days 2026? Please inquire at info@scaladays.org. Follow us and share on Mastodon, Bluesky, LinkedIn. To get early updates and special offers, please sign up for the mailing list. Join the #scala-days channel on the Scala Discord to chat with fellow attendees. Call for talk and workshop proposals opens late April 2026.

## Porting the Scala 2 optimizer to Scala 3

DevFeed: [Porting the Scala 2 optimizer to Scala 3](<https://devfeed.tech/articles/porting-the-scala-2-optimizer-to-scala-3-43560.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/03/23/porting-the-optimizer.html>)

Published: 2026-03-22T23:00:00Z

Content type: article

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Closure](<https://devfeed.tech/topics/closure.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [compiler](<https://devfeed.tech/tags/compiler.md>), [functional](<https://devfeed.tech/tags/functional.md>), [performance](<https://devfeed.tech/tags/performance.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

This post explains the work to port the Scala 2 optimizer to the Scala 3 compiler. The goal is to improve the performance of high-level functional Scala code without requiring developers to write more complex low-level code; early microbenchmarks reported 10-30% faster execution.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: Maintenance of the Standard Library/Core Library Modules and APIs. The work is coordinated by the Scala Center. We are porting the optimizer from the Scala 2 compiler to the Scala 3 compiler, improving the performance of Scala 3 applications without requiring developers to write more complex code. In early microbenchmarks of code written in a high-level functional style, we're seeing 10-30% faster execution. But what exactly is this optimizer and why is it necessary? This work is available as of version 3.8.3-RC3 of the Scala compiler. Scala is a modern and concise language, meaning you can write code expressing what you want to do by composing primitives, rather than how to do it step-by-step. High-level code is easier to read and maintain, in addition to being shorter to write. Scala's expressiveness enables you to write what you mean: def addOneMap(a: Array[Int]) = a.map(_ + 1) However, from a CPU's point of view, a high-level API like map is conceptually more complex than the equivalent low-level code. It's a function call that is passed another function, leading to a "megamorphic" call site that is harder for the JVM to optimize, and the function argument might need a closure to be allocated on the heap if it captures local values. Compiled naïvely, the high-level call wouldn't be as fast as this equivalent low-level loop: def addOneLoop(a: Array[Int]) = val l = a.length val r = new Array[Int](l) var i = 0 while i < l do r(i) = a(i) + 1 i += 1 r You don't want to write this loop, because its purpose is a lot less obvious and it is harder to maintain, but without compiler help, you might have to write it if that function is critical to your application's performance. (Why would adding one to an array be critical to your app's performance? Because you're reading a pedagogical blog post and thus suspending disbelief!) If you've ever written a map function yourself, you may recognize the

## Hardening Scoverage Support in Scala 3

DevFeed: [Hardening Scoverage Support in Scala 3](<https://devfeed.tech/articles/hardening-scoverage-support-in-scala-3-43559.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/03/11/scoverage.html>)

Published: 2026-03-10T23:00:00Z

Content type: article

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ci](<https://devfeed.tech/tags/ci.md>), [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The Scala Center reports progress hardening Scoverage, Scala's code coverage tool, for Scala 3. The work expands testing across compiler language features and the compiler's CI test suite, identifying and addressing compatibility and reliability issues.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: Scoverage hardening. The work is coordinated by the Scala Center. Summary Code coverage is a key part of maintaining high-quality Scala projects. We've recently made progress on making Scoverage more robust for Scala 3, expanding the way we test it and discovering and fixing new issues. Background Measuring how much of your Scala code is exercised by tests sounds simple until you try to do it yourself. That's where code coverage tools come in. Code coverage is not optional for many organizations. As one of the QA metrics, coverage helps ensure reliability of the solution which is especially important in regulated sectors. Scoverage is the standard coverage tool for Scala, built directly into the Scala 3 compiler as a dedicated phase. A crucial requirement for Scoverage's wide industry adoption is that Scoverage itself is reliable and well-tested. The tool is already tested via its own dedicated test suite - however, that is not enough. Most tricky bugs happen not in isolation but at intersections of language features. Therefore, Scoverage needs to be tested in interaction with all of the language features to be truly considered reliable. Furthermore, all future changes to the compiler should be tested in interaction with Scoverage to ensure the tool remains compatible with the compiler. To guarantee such a level of reliability, we have recently started a systematic rework of the testing strategy for Scoverage. This article reports on the progress we've made in 2026 so far. Enabling coverage on the compiler test suite The first step was mapping out the current failures of Scoverage in interaction with other language features. The strategy for that was to enable Scoverage on the existing compiler test suite. This means, in addition to the usual CI run of the tests that we do for each new PR, now we run the same tests again, but with Scoverage enabled. Under this mode, for each test we verify

[Next page](<https://devfeed.tech/sources/the-scala-programming-language.md?cursor=WyIyMDI2LTAzLTEwVDIzOjAwOjAwKzAwOjAwIiwgIjY5MTg2YWEzLWZkMzQtNGZjZS04NDI5LTc2NmRmOTc2ZmY5MSJd>)