[dependabot]

Bumps the gradle-deps group with 3 updates in the / directory: gradle-wrapper, org.jetbrains.kotlinx:kotlinx-serialization-json and io.lettuce:lettuce-core.

Updates gradle-wrapper from 9.8.1 to 9.8.2

Release notes

Sourced from gradle-wrapper's releases.

9.8.2

The Gradle team is excited to announce Gradle 9.8.2.

Here are the highlights of this release:

• Java 27 support
• Maven mirror settings reuse
• Linked problem locations in build output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle: Aman Gautam, Björn Kautler, Eng Zer Jun, Hashim Khan, Julian Krannich, KBS, Labh R Jethe, Mark Dodgson, Maxim, monkey, nataphon-ktsystems, Paul King, Qiu Tian, rg_sandesh, Roberto Perez Alcolea, Sean, Zongle Wang.

Upgrade instructions

Switch your build to use Gradle 9.8.2 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.8.2 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

Commits

• 8de7bcf Speed up the AllVersionsCrossVersion flaky quarantine (#39494)
• 66805db Run all cross-version targets in flaky quarantine
• cdd4c8f Skip empty test tasks in the flaky test quarantine
• 6badb77 Split the AllVersionsCrossVersion quarantine across agents
• 1655e44 Prepare for 9.8.2 (#39492)
• 6702214 Prepare for 9.8.2
• 688c0c1 Fix false warning about unstable graph (#39479)
• 3601d4f Clarify selector reuse comments in SelectorState
• 6e836fd Fix false warning about unstable graph
• a0790e5 Fix hidden artifact cleanup pattern in CheckProject (#39451)
• Additional commits viewable in compare view

Updates org.jetbrains.kotlinx:kotlinx-serialization-json from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

• Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
• Correctly decode CborLabel values (#3195)
• Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

• 4c28c3e 1.12.0 release (#3295)
• abe8a96 Merge remote-tracking branch 'origin/master' into dev
• 952d17a Added Gradle task to prepare release (#3279)
• 6f30025 Remove Play verification files (#3266)
• 89b23ca Workaround watchosArm32 removal (#3291)
• 53932a0 Update links to Okio site and its docs (#3292)
• 3a5db3b Reduce the number of input fields for bug report
• 9ede0e2 Added templates to the issue creation wizard
• 5d3f884 Update Dokka to version 2.3.0-Beta (#3286)
• 1fe9a49 Suppress deprecation of nodejs in wasmWasi configuration (#3287)
• Additional commits viewable in compare view

Updates io.lettuce:lettuce-core from 6.8.2.RELEASE to 6.9.0.RELEASE

Release notes

Sourced from io.lettuce:lettuce-core's releases.

6.9.0.RELEASE

The Lettuce team is pleased to announce the Lettuce 6.9.0 release! This release changes how commands are rejected while a connection is not available. Read the behavior change below before you upgrade.

Lettuce 6 supports Redis 2.6+ up to Redis 8.2. In terms of Java runtime, Lettuce requires at least Java 8 and works with Java 21.

Thanks to all contributors who made Lettuce 6.9.0 possible.

• GitHub Discussions: https://github.com/lettuce-io/lettuce-core/discussions
• Stack Overflow (Questions): https://stackoverflow.com/questions/tagged/lettuce
• Join the chat at https://discord.gg/redis and look for the "Help:Tools Lettuce" channel
• GitHub Issues (Bug reports, feature requests): https://github.com/lettuce-io/lettuce-core/issues
• Documentation: https://lettuce.io/core/6.9.0.RELEASE/reference/
• Javadoc: https://lettuce.io/core/6.9.0.RELEASE/api/

Behavior change

This applies when commands are rejected while disconnected: with DisconnectedBehavior.REJECT_COMMANDS, or with DisconnectedBehavior.DEFAULT and auto-reconnect disabled.

• Redis Cluster: a command now fails right away when the connection to its target node is still being established, for example the first commands to a node after startup, or after a new slot mapping appears. This also applies to commands redirected with MOVED/ASK. Before, these commands waited for the connection attempt, up to the connect timeout.
• All connection types: when writing a command to the channel fails, the command is now rejected instead of being re-queued.

To avoid rejections right after startup, connect to the cluster nodes up front.

This change is also in 7.7.0 and later. The 7.0.x – 7.6.x lines do not include it.

Fixes

• DisconnectedBehavior.REJECT_COMMANDS does not fail fast for Redis Cluster commands waiting on lazy node connection establishment in redis/lettuce#3747 (backport of redis/lettuce#3782 by @​Vaibhav026)

Full Changelog: redis/lettuce@6.8.2.RELEASE...6.9.0.RELEASE

Changelog

Sourced from io.lettuce:lettuce-core's changelog.

Lettuce 6.9.0 RELEASE NOTES

The Lettuce team is pleased to announce the Lettuce 6.9.0 release! This release changes how commands are rejected while a connection is not available. Read the behavior change below before you upgrade.

Lettuce 6 supports Redis 2.6+ up to Redis 8.2. In terms of Java runtime, Lettuce requires at least Java 8 and works with Java 21.

Thanks to all contributors who made Lettuce 6.9.0 possible.

• GitHub Discussions: https://github.com/lettuce-io/lettuce-core/discussions
• Stack Overflow (Questions): https://stackoverflow.com/questions/tagged/lettuce
• Join the chat at https://discord.gg/redis and look for the "Help:Tools Lettuce" channel
• GitHub Issues (Bug reports, feature requests): https://github.com/lettuce-io/lettuce-core/issues
• Documentation: https://lettuce.io/core/6.9.0.RELEASE/reference/
• Javadoc: https://lettuce.io/core/6.9.0.RELEASE/api/

Behavior change

This applies when commands are rejected while disconnected: with DisconnectedBehavior.REJECT_COMMANDS, or with DisconnectedBehavior.DEFAULT and auto-reconnect disabled.

• Redis Cluster: a command now fails right away when the connection to its target node is still being established, for example the first commands to a node after startup, or after a new slot mapping appears. This also applies to commands redirected with MOVED/ASK. Before, these commands waited for the connection attempt, up to the connect timeout.
• All connection types: when writing a command to the channel fails, the command is now rejected instead of being re-queued.

To avoid rejections right after startup, connect to the cluster nodes up front.

This change is also in 7.7.0 and later. The 7.0.x – 7.6.x lines do not include it.

Fixes

• DisconnectedBehavior.REJECT_COMMANDS does not fail fast for Redis Cluster commands waiting on lazy node connection establishment in redis/lettuce#3747 (backport of redis/lettuce#3782 by @​Vaibhav026)

Full Changelog: redis/lettuce@6.8.2.RELEASE...6.9.0.RELEASE

Commits

• cc883e1 Add maven wrapper (#3951)
• f4bef00 Fix snapshot and release publishing with Maven 3.10 credential scoping (#3940)
• f3947a7 Reset shared client options after AtMostOnceIntegrationTests
• c60a3e5 Raise memlock limit for io_uring in integration tests
• 9dd089f Release 6.9.0
• e88c506 Fix/cluster reject commands pending future (#3782)
• See full diff in compare view

[github-actions]

Thanks for opening your first pull request on guard-core-jvm!

Quick checklist before review (most of these are enforced by CI, but worth a glance):

• The PR body says Closes #N for an open issue (the issue-link check enforces it); chores take the no-issue label
• ./gradlew spotlessCheck detekt is clean
• ./gradlew build passes
• The conformance smoke is green: ./gradlew :guard-core-conformance:test (a flipped corpus case needs a ledger or xfail update with a written reason)
• No blanket @Suppress in non-test code; the CHANGELOG.md entry for the current version mentions the change

See AGENTS.md for the boundary rules (the engine module stays dependency-free; conformance data is vendored byte-identical, never hand-edited) and the mirror-lockstep versioning note.

Welcome aboard - a maintainer will review shortly.

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.