[dependabot]

Bumps com.esotericsoftware:kryo from 5.6.2 to 5.7.1.

Release notes

Sourced from com.esotericsoftware:kryo's releases.

kryo-5.7.1

This is a maintenance release that fixes the serializers for unmodifiable and synchronized collections introduced in 5.7.0.

Highlights

Registration in a fixed order (#1351)

registerSerializers registered the wrapper classes in HashMap order, so their registration IDs depended on the JVM: eg the unmodifiable list had ID 11 on JDK 17 and 13 on JDK 21. Data written on one JVM could be read as a different wrapper type on another. The new register(Kryo) registers the classes, including the navigable wrappers, in a fixed order:

UnmodifiableCollectionSerializers.register(kryo);
SynchronizedCollectionSerializers.register(kryo);

registerSerializers is deprecated and keeps its IDs, so existing data stays readable. See the upgrade notes below before switching.

Navigable and sequenced wrappers (#1351)

addDefaultSerializers of UnmodifiableCollectionSerializers and SynchronizedCollectionSerializers didn't cover the navigable wrappers (eg Collections.unmodifiableNavigableSet) and the Java 21+ unmodifiable sequenced wrappers (eg Collections.unmodifiableSequencedCollection). These were silently read back as a different wrapper type, eg an UnmodifiableNavigableSet as an UnmodifiableSortedSet. They are now serialized correctly. The serialized bytes are unchanged, so 5.7.0 and 5.7.1 can read each other's data.

All changes

• #1351 Add serializers for navigable and sequenced wrapper collections and register them in a fixed order

The full list of changes can be found here.

Many thanks to all contributors!

Upgrade Notes

For migration from previous major versions please check out the migration guide. We're asking the community to help and contribute this part: please edit the migration wiki page as you encounter any information or issues that might help others.

Behavioral changes

• If you use registerSerializers, switch to register(Kryo). It registers the 9 wrapper classes of each type in a different order, so their registration IDs change once: data written with registerSerializers can't be read after switching to register. Switch when you don't need to read previously written data that contains these wrappers, or keep registerSerializers until then.
• register(Kryo) throws an exception if the JDK internals can't be accessed, while the deprecated registerSerializers logged a warning and skipped the registration. addDefaultSerializers still logs a warning.
• register(Kryo) doesn't register the Java 21+ sequenced wrappers, so that the same classes are registered on all Java versions. After addDefaultSerializers, they can be registered with kryo.register(Class).

Compatibility

• Serialization compatible
  • Standard IO: Yes
  • Unsafe-based IO: Yes
• Binary compatible - Yes (Details)
• Source compatible - Yes (Details)

kryo-5.7.0

This is a feature release that hardens deserialization against corrupt or malicious input, adds long-requested serializers for unmodifiable and synchronized JDK collections, and fixes several bugs. It also improves compatibility with recent JDKs up to Java 26.

Highlights

... (truncated)

Commits

• b9089cb [maven-release-plugin] prepare release kryo-parent-5.7.1
• 6f0803c Add serializers for navigable and sequenced wrapper collections and register ...
• d6dfef1 Update README for 5.7.0
• fda2ee5 Add compat report for 5.7.0
• 40971e7 [maven-release-plugin] prepare for next development iteration
• ae331b6 [maven-release-plugin] prepare release kryo-parent-5.7.0
• 47a300d Make unmodifiable and synchronized collection serializer classes final
• c7976d6 Compile main sources for Java 8 regardless of JDK
• 96b9b62 Fix duplicate tag error message in TaggedFieldSerializer
• 39294ec Document that maxDepth also limits deserialization work
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)