You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changes since 0.12.2 on the 0.12.x maintenance branch.
Parsing fixes
Check unsigned integer ranges before expanding exponents, avoiding expensive
integer conversion for out-of-range values such as 1e100000000. Valid unsigned
boundaries and integral decimal/exponent forms remain supported.
Treat enum integers outside the signed 32-bit range as invalid instead of
truncating them into potentially valid values. Proto3 parsing with ignoringUnknownFields retains its fallback to the zero enum value.
Preserve google.protobuf.NullValue oneof presence when reading JSON null.
Supplying another member of the same oneof now triggers overlap validation
instead of silently ignoring the null-valued member.
Accept standard and URL-safe Base64 bytes, with or without padding. Preserve
all forms accepted by the legacy decoder, including its whitespace handling.
Malformed Base64 now raises JsonFormatException rather than leaking the
decoder's IllegalArgumentException.
Preserve existing parsing defaults: this branch does not introduce master's
100-container nesting limit or 1024-character numeric-literal limit.
Dependencies and platform support
Update ScalaPB from 0.11.18 to 0.11.21, protobuf-java from 3.25.8 to 3.25.9, and json4s from 4.0.6 to 4.0.7.
Retain the ScalaPB 0.11.x, protobuf 3.x, and json4s 4.0.x dependency lines.
Update the Scala cross-build versions to 2.12.21, 2.13.18, and 3.3.8.
Retain Java 8 runtime support for all Scala builds. Building the project now
requires JDK 11 or newer, with explicit Java 8 bytecode and API targets.
Build and release validation
Validate all Scala builds on Java 8, 11, and 21, and check binary compatibility
against 0.12.2.
Run tests, formatting, and binary-compatibility checks on tag revisions before
publishing. Modernize publishing metadata and release tooling.
#1226 [2.10.x] Avoid running out of memory when parsing heavily nested arrays or objects by @mkurz
We now limit the maximum allowed nesting depth of JSON structures (arrays, objects, or a mix of both) to 1000.
This limit can be adjusted using the system property play.json.parser.maxNestingDepth.
We assume a depth of 1000 should be more than sufficient for virtually all real-world use cases.
This change helps prevent both potential OutOfMemoryErrors and StackOverflowErrors.
The latter, however, is not a concern for Play JSON, since it already uses a @tailrec-optimized parsing method.
As a result, Play JSON is not affected by CVE-2025-52999, which specifically addresses StackOverflowError risks.
This improvement is simply an additional safety measure.
If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.
🙇 Thanks to our contributors
Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!
If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.
🙇 Thanks to our contributors
Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!
fix: a requireAuth value that excludes every authentication method, such as !password,!md5,!gss,!sspi,!scram-sha-256,!none, now refuses every method. A connection with such a value now fails with SQLState 08004. Before, the driver treated the value as if requireAuth were not set, and used any method the server asked for, even a cleartext password. This affects 42.7.11 through 42.7.13 GHSA-rhp9-mr79-r74h
fix: a requireAuth value without a method in it, such as , or ,,, now fails with SQLState 22023. Before, the driver treated it as if requireAuth were not set. Commas at the very end of a value are still ignored, as in password,. This affects 42.7.11 through 42.7.13 GHSA-rhp9-mr79-r74h
fix: a value shorter than its declared length, such as one from a ByteStreamWriter whose getLength() is larger than what writeTo() writes, is now padded with zeros. Before, the driver padded it with bytes of messages sent earlier on the same connection, so the stored value could contain SQL text and parameter values of earlier statements. This affects 42.7.4 through 42.7.13 GHSA-f64h-wr5q-3qf3
Based on the git blame history of the changed files, we recommend the following reviewers:
Committers with relevant context:@parshimers
You can request their reviews formally with /request-review @parshimers.
Contributors with relevant context:@Ma77Ball, @aglinxinyuan, @carloea2
You can notify them by mentioning @Ma77Ball, @aglinxinyuan, @carloea2 in a comment.
Compared against main 55e179a benchmarked on this same runner, so the delta is largely free of cross-runner hardware noise. The "7d avg" column still reflects the gh-pages dashboard. Treat <±5% as noise unless repeated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
0.14.7→0.14.102.9.0→2.9.23.14.2→3.14.50.11.20→0.11.210.12.0→0.12.30.12.2→0.12.32.10.6→2.10.83.9.5→3.9.61.4.9→1.4.101.4.6→1.4.101.5.1→1.5.21.5.2→1.5.34.0.7→4.0.174.0.7→4.0.171.3.23→1.3.291.3.23→1.3.294.0.7→4.0.174.0.7→4.0.171.3.23→1.3.294.0.7→4.0.174.8.184→4.8.2004.8.157→4.8.2004.8.184→4.8.20021.0.0→21.0.2-legacy4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final4.2.15.Final→4.2.21.Final3.2→3.2.11.7.0→1.7.11.7.0→1.7.11.7.0→1.7.11.7.0→1.7.11.7.0→1.7.11.7.0→1.7.11.7.0→1.7.11.7.0→1.7.11.7.0→1.7.10.9.6→0.9.79.4.20.v20190813→9.4.58.v202508149.4.20.v20190813→9.4.58.v2025081411.0.24→11.0.269.4.20.v20190813→9.4.58.v202508145.13.0.202109080827-r→5.13.5.202508271544-r0.4.3→0.4.442.7.13→42.7.1442.7.10→42.7.143.2.15→3.2.203.2.17→3.2.201.7.26→1.7.36Release Notes
scalacenter/sbt-scalafix (ch.epfl.scala:sbt-scalafix)
v0.14.10Compare Source
Pull Requests
v0.14.9Compare Source
Pull Requests
v0.14.8Compare Source
Pull Requests
scalapb/scalapb-json4s (com.thesamet.scalapb:scalapb-json4s)
v0.12.3Compare Source
Changes since
0.12.2on the0.12.xmaintenance branch.Parsing fixes
integer conversion for out-of-range values such as
1e100000000. Valid unsignedboundaries and integral decimal/exponent forms remain supported.
truncating them into potentially valid values. Proto3 parsing with
ignoringUnknownFieldsretains its fallback to the zero enum value.google.protobuf.NullValueoneof presence when reading JSONnull.Supplying another member of the same oneof now triggers overlap validation
instead of silently ignoring the null-valued member.
all forms accepted by the legacy decoder, including its whitespace handling.
Malformed Base64 now raises
JsonFormatExceptionrather than leaking thedecoder's
IllegalArgumentException.100-container nesting limit or 1024-character numeric-literal limit.
Dependencies and platform support
0.11.18to0.11.21, protobuf-java from3.25.8to3.25.9, and json4s from4.0.6to4.0.7.2.12.21,2.13.18, and3.3.8.requires JDK 11 or newer, with explicit Java 8 bytecode and API targets.
Build and release validation
against
0.12.2.publishing. Modernize publishing metadata and release tooling.
v0.12.2Compare Source
v0.12.1Compare Source
playframework/play-json (com.typesafe.play:play-json)
v2.10.8: Play JSON 2.10.8Compare Source
Noteworthy improvements
This limit can be adjusted using the system property
play.json.parser.maxNestingDepth.We assume a depth of 1000 should be more than sufficient for virtually all real-world use cases.
This change helps prevent both potential
OutOfMemoryErrors andStackOverflowErrors.The latter, however, is not a concern for Play JSON, since it already uses a
@tailrec-optimized parsing method.As a result, Play JSON is not affected by CVE-2025-52999, which specifically addresses
StackOverflowErrorrisks.This improvement is simply an additional safety measure.
Changes
❤️ Thanks to our premium sponsors!
If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.
🙇 Thanks to our contributors
Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!
v2.10.7: Play JSON 2.10.7Compare Source
Noteworthy Scala 3 improvements
Changes
Dependency Graphaction (backport #1114) by @ihostage by @mergify[bot]❤️ Thanks to our premium sponsors!
If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.
🙇 Thanks to our contributors
Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!
lightbend/scala-logging (com.typesafe.scala-logging:scala-logging)
v3.9.6Compare Source
What's Changed
New Contributors
Full Changelog: scala-garden/scala-logging@v3.9.5...v3.9.6
lightbend/config (com.typesafe:config)
v1.4.10Compare Source
What's Changed
New Contributors
Full Changelog: lightbend/config@v1.4.9...v1.4.10
altoo-ag/pekko-kryo-serialization (io.altoo:pekko-kryo-serialization)
v1.5.2Compare Source
What's Changed
Full Changelog: altoo-ag/pekko-kryo-serialization@v1.5.1...v1.5.2
altoo-ag/scala-kryo-serialization (io.altoo:scala-kryo-serialization)
v1.5.3Compare Source
What's Changed
Full Changelog: altoo-ag/scala-kryo-serialization@v1.5.2...v1.5.3
kubernetes-client/java (io.kubernetes:client-java)
v21.0.2-legacyCompare Source
[maven-release-plugin] copy for tag v21.0.2-legacy
v21.0.1Compare Source
v21.0.0-legacyCompare Source
apache/pekko (org.apache.pekko:pekko-actor)
v1.7.1Compare Source
ehcache/sizeof (org.ehcache:sizeof)
v0.4.4Compare Source
pgjdbc/pgjdbc (org.postgresql:postgresql)
v42.7.14Security
requireAuthvalue that excludes every authentication method, such as!password,!md5,!gss,!sspi,!scram-sha-256,!none, now refuses every method. A connection with such a value now fails with SQLState08004. Before, the driver treated the value as ifrequireAuthwere not set, and used any method the server asked for, even a cleartext password. This affects 42.7.11 through 42.7.13 GHSA-rhp9-mr79-r74hrequireAuthvalue without a method in it, such as,or,,, now fails with SQLState22023. Before, the driver treated it as ifrequireAuthwere not set. Commas at the very end of a value are still ignored, as inpassword,. This affects 42.7.11 through 42.7.13 GHSA-rhp9-mr79-r74hByteStreamWriterwhosegetLength()is larger than whatwriteTo()writes, is now padded with zeros. Before, the driver padded it with bytes of messages sent earlier on the same connection, so the stored value could contain SQL text and parameter values of earlier statements. This affects 42.7.4 through 42.7.13 GHSA-f64h-wr5q-3qf3scalatest/scalatest (org.scalatest:scalatest)
v3.2.20Compare Source
v3.2.19Compare Source
v3.2.18Compare Source
v3.2.17Compare Source
[
v3.2.16](httConfiguration
📅 Schedule: (in timezone Etc/UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.