Repository navigation
chore(deps): update sbt patch updates - #7730
Open
renovate-bot wants to merge 1 commit into
Open
renovate-bot wants to merge 1 commit into
renovate-bot wants to merge 1 commit into
Conversation
forking-renovate
Bot
added
the
dependencies
Contributor
Automated Reviewer SuggestionsBased on the
|
Contributor
✅ No material benchmark regressions detected🟢 4 better · 🔴 0 worse · ⚪ 11 noise (<±5%) · 0 without baseline
Baseline detailsLatest main
Raw CSVconfig_idx,batch_size,schema_width,string_len,num_batches,total_ms,total_tuples,total_bytes,tuples_per_sec,mb_per_sec,lat_p50_us,lat_p95_us,lat_p99_us
0,10,10,64,20,298.64,200,128000,670,0.409,14039.82,20777.39,20777.39
1,100,10,64,20,1239.30,2000,1280000,1614,0.985,60612.54,72963.02,72963.02
2,1000,10,64,20,10395.52,20000,12800000,1924,1.174,514942.09,588850.55,588850.55 |
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
from
August 20, 2026 19:48
922a600 to
c5ff703
Compare
❌ 2 Tests Failed:
View the top 2 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
3 times, most recently
from
August 25, 2026 07:49
6470867 to
02d2c2b
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
3 times, most recently
from
September 3, 2026 10:50
473dd01 to
2a9148b
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
from
September 7, 2026 01:37
2a9148b to
031d798
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
3 times, most recently
from
September 13, 2026 23:37
3cd5b26 to
f525282
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
2 times, most recently
from
September 19, 2026 00:51
e05af9e to
c8381d9
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
3 times, most recently
from
September 26, 2026 20:58
354b67d to
eae906d
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
3 times, most recently
from
October 8, 2026 08:31
0cd3f2f to
a2594c0
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
2 times, most recently
from
October 18, 2026 22:32
b6b65fb to
5d1f6a9
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
from
October 22, 2026 22:35
5d1f6a9 to
b53d238
Compare
renovate-bot
force-pushed
the
renovate/sbt-patch-updates
branch
from
October 25, 2026 17:21
b53d238 to
1e1c4d9
Compare
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.90.14.6→0.14.92.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.6→1.4.91.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.1994.8.157→4.8.1994.8.184→4.8.19921.0.0→21.0.2-legacy4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.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.43.1.0-M1→3.1.0-M1042.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.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.9Compare Source
What's Changed
New Contributors
Full Changelog: lightbend/config@v1.4.8...v1.4.9
v1.4.8Compare Source
What's Changed
Full Changelog: lightbend/config@v1.4.7...v1.4.8
v1.4.7Compare Source
What's Changed
New Contributors
Full Changelog: lightbend/config@v1.4.6...v1.4.7
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.13Added
search_pathchange via GUC_REPORT (PostgreSQL 18+), so cached plans are no longer used against the wrong schema PR #4259reWriteBatchedInsertsnow merges up to 32768 rows into one multi-valuesINSERT(bounded by the 65535 bind-parameter limit on the extended protocol) instead of capping at 128, which speeds up batches of few-column rows. The newreWriteBatchedInsertsSizeconnection property lowers that cap when set; the default of0uses that maximum. PR #4207autosave=ALWAYS. Controlled by the newflushCacheOnDdlconnection property (defaulttrue); set tofalsefor the prior behaviour. PR #4067connectExecutorconnection property to customize theExecutorused to run the worker task that performs the connection attempt whenloginTimeoutis in effect. The value is the fully qualified name of a class implementingjava.util.concurrent.Executor. With a null value, the default, the driver retains the prior behavior of running the connection attempt on a daemon thread named"PostgreSQL JDBC driver connection thread". The executor must run the task on a thread other than the caller's. Running the attempt on a named thread lets applications that monitor driver-created threads identify it. PR #4165classLoaderStrategyconnection property to control which classloaders the driver searches when loading a class named by a connection property, for examplesocketFactory. The defaultdriver-firstnow falls back to the thread context classloader when the driver's classloader cannot resolve the class, which fixes class loading in non-flat class paths such as Quarkus and OSGi. Setdriverto keep the previous driver-classloader-only behaviour, orcontext-firstto prefer the thread context classloader Issue #2112 PR #4167RECORD, andrefcursorPR #4220LargeObjectBlobInputStreamnow skips by seeking instead of reading, and the driver exposes the server version so it can select the 64-bit large-object API where available PR #4204Changed
loginTimeoutis now aFutureTask(ConnectTask) instead of the hand-rolledConnectThread. When the caller hits the timeout, the task is now cancelled withcancel(true), which interrupts the worker thread rather than letting it run to completion. This makes the connection attempt interruptible, sologinTimeoutcan stop a slow connection attempt instead of leaking a thread. As before, a connection that the worker still manages to establish after the caller gives up is closed by the worker so that it does not leak. There are no public API changes and this should only lead to faster background resource cleanup for connections that time out. PR #4120PGXAConnection.ConnectionHandlernow rejectssetAutoCommit(false)andsetSavepoint(...)during an active XA branch, in addition to the long-rejectedsetAutoCommit(true)/commit()/rollback(). ThesetSavepointrejection was already meant to be in place but the guard misspelled the method name assetSavePoint, so savepoints silently went through. Both changes bring the proxy in line with JTA 1.2 §3.4. PR #4114commitPrepared/rollback-of-prepared now returnXAER_RMFAILinstead ofXAER_RMERRwhen the underlying connection is left in a non-idleTransactionState. Transaction managers (Geronimo, Narayana, Atomikos) treatXAER_RMFAILas retryable on a freshXAResource; the prepared transaction is no longer abandoned. PR #4114getPrimaryKeysfrompg_constraint.conkeyPR #4202Fixed
postgresql-<version>.jarand its detached PGP signature, taken from the same signed build that is uploaded to Maven Central, instead of a leftover SNAPSHOT jar Issue #3812 PR #3814Statement#cancelstate machine by dropping the redundantCANCELLEDstate.killTimerTasknow waits for the state to return toIDLEdirectly, which removes a spin-forever case when more than one thread observes the cancel completing PR #1827.BEGINand the following query to share a network flush Issue #3894 PR #4196reWriteBatchedInsertsno longer throwsIllegalArgumentExceptionwhen batching a parameterlessINSERT(for exampleINSERT INTO t VALUES (1, 2)) of 256 rows or more PR #4207CALLin aCallableStatementno longer hides the native call, so OUT parameter registration works for/* comment */ call proc(?, ?)and similar.Parser.modifyJdbcCallnow skips leading whitespace and SQL comments (both--and/* */) before the call, tolerates a trailing comment after a{ ... }escape, and no longer adds a spurious comma when moving an OUT parameter into a call whose arguments are only a comment Issue #2538 PR #4209PreparedStatement.toString()no longer throws for abyteavalue supplied as text viaPGobject. Hex-format values (\x...) are validated and rendered as abytealiteral, and escape-format values are quoted and cast like any other literal Issue #3757 PR #4201contextClassLoaderof sharedForkJoinPool.commonPool()worker threads, which previously left unrelated tasks on those threads running with anullclassloader Issue #4155 PR #4156PgResultSet#getCharacterStreamwrapsStringin aStringReaderPR #4063PGXAConnectionno longer saves and restores the underlying connection's JDBCautoCommitflag. All XA-protocol SQL (BEGIN,PREPARE TRANSACTION,COMMIT,ROLLBACK,COMMIT PREPARED,ROLLBACK PREPARED, therecover()SELECT) is sent throughQUERY_SUPPRESS_BEGIN, so the caller'sautoCommitvalue is invariant across everyXAResourcecall. Fixes the "2nd phase commit must be issued using an idle connection" failure during recovery on managed datasources that pool connections withautoCommit=false(TomEE, WildFly, WebSphere Liberty) PR #4114PGXAConnection.prepare()now mutates XA state only afterPREPARE TRANSACTIONsucceeds. A failedPREPAREpreviously left the driver thinking the branch was already prepared, so the follow-uprollback(xid)triedROLLBACK PREPAREDagainst a non-existent gid and returnedXAER_RMERR. Transaction managers (Narayana) escalated this toHeuristicMixedException. With the fix,rollback(xid)takes the active-branch path and issues a plainROLLBACK, which the server accepts cleanly. Fixes Issue #3153, Issue #3123. PR #4114search_path. When two schemas held a table with the same name and the same primary or unique index name but a different set of key columns, the driver took the union of both schemas' columns, so the result set could be wrongly rejected as not updatable PR #4214. Supersedes PR #3400.LargeObject.close()now flushes a buffered output stream before marking the object closed, so closing a large object without an explicitflush()no longer drops buffered writes. The flush runs while the object is still open (it calls back intoLargeObject.write()), andlo_closealways runs afterward; a failure fromlo_closeno longer masks an earlier flush error, and the transaction is not committed when the flush failed Issue #4247 PR #4248.timestamp,timestamptz, anddatetext with a clearSQLException(SQLState22007) instead of anArrayIndexOutOfBoundsExceptionPR #4278CHAR_OCTET_LENGTHfor non-character columns PR #4231ResultSet.getBigDecimal(int, int)PR #4211java.timevalues in an updatableResultSetupdateRow()/insertRow()PR #3848RETURNINGclause containsvarcharornumerictypes PR #4014estimatedReceiveBufferBytesaccounting after a forcedSyncPR #4014ResultSetfor describe-statement purposes, and restore the pre-describe path for generated-key batches PR #4014search_pathchanges case-insensitively PR #4216.keyextension PR #3946KeyStoreso FIPS JVMs work [PR #4193](https://rediConfiguration
📅 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.