Skip to content

Update scala3-library to 3.3.9 - #1386

Merged
pjfanning merged 3 commits into
apache:mainfrom
scala-steward:update/scala3-library-3.3.9
Oct 28, 2026
Merged

pjfanning merged 3 commits into
apache:mainfrom
scala-steward:update/scala3-library-3.3.9

Conversation

@scala-steward

Copy link
Copy Markdown
Contributor

About this PR

📦 Updates org.scala-lang:scala3-library from 3.3.8 to 3.3.9

📜 GitHub Release Notes - Version Diff - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala3-library" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, commit-count:1

scala-steward and others added 3 commits October 28, 2026 16:10
Motivation:
Scala 3.3.9 emits more complete Java generic signatures than 3.3.8, so MiMa
reports 127 IncompatibleSignatureProblems in http and http-core. Erased
descriptors are unchanged, so runtime binary compatibility is unaffected.

Modification:
Add a MiMaSignatureProblems auto plugin that requires the sbt-pekko-build MiMa
plugin (which sets mimaReportSignatureProblems := true) and overrides it to
only report signature problems on Scala 2.13. Drop the setting from Common,
which was applied before the sbt-pekko-build plugin and had no effect.

Result:
MiMa passes on Scala 3.3.9 without a large excludes file.

Tests:
- sbt "++3.3.9" http-core/mimaReportBinaryIssues http/mimaReportBinaryIssues: success
- show mimaReportSignatureProblems: false on 3.3.9, true on 2.13

References:
Refs apache/pekko#3538
Motivation:
The validatePullRequest MiMa check calls SbtMima.runMima directly and skipped
the mimaReportSignatureProblems filter that mimaReportBinaryIssues applies, so
the Scala 3 build still failed on 127 IncompatibleSignatureProblems.

Modification:
Drop IncompatibleSignatureProblems from the reported problems when
mimaReportSignatureProblems is false.

Result:
validatePullRequest passes on Scala 3.3.9; signature problems are still reported
on Scala 2.13.

Tests:
- sbt "++3.3.9" "show http/mimaResult" "show http-core/mimaResult": NoErrors
- sbt "show http/mimaResult" "show http-core/mimaResult" (2.13): NoErrors

References:
Refs apache/pekko#3538
@pjfanning
pjfanning merged commit c525ae2 into apache:main Oct 28, 2026
6 checks passed
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.

3 participants