Bump kryo from 4.0.1 to 5.0.1

[dependabot-preview]

Bumps kryo from 4.0.1 to 5.0.1.

Release notes

Sourced from kryo's releases.

kryo-5.0.1

This is a maintenance release coming with fixes and improvements.

#777: Fix #776 Automatic module name #779: Dependency Upgrades #780: Fix #778 Use canonical class name for registration hint if available #787: Fix #786 Ensure field serializers balance pushGenericType and popGenericType calls #788: Fix #774, #784 Do not re-use serializers for CompatibleFieldSerializer and TaggedFieldSerializer #790: Fix #789 Catch StackOverflowError and add hint for enabling references

The full list of changes can be found here.

Many thanks to all contributors!

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.

Compatibility

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

kryo-5.0.0

This is the final release of the new major version 5.0.0 of Kryo (see also the RC1 release notes for major changes of v5).

This version comes with only minor changes on top of RC9 (the list of changes from RC9 can be found here). For a detailed list of changes to 4.x please go though the release notes for the release candidates for kryo 5.

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.

Compatibility

Due to big changes 5.0.0 is both source/binary incompatible and serialization incompatible to previous major versions - for details see the RC1 compatibility report and those of the subsequent RCs.

Compatibility of 5.0.0 to RC9:

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

kryo-5.0.0-RC9

This is the 9th release candidate of the new major version of Kryo (see also the RC1 release notes for major changes of v5).

This RC comes with significant performance improvements. The exact list of changes from RC8 to RC9 can be found here.

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.

Compatibility

Commits

• 4f212fc [maven-release-plugin] prepare release kryo-parent-5.0.1
• 816cfcd [maven-release-plugin] rollback the release of kryo-parent-5.0.1
• c529136 [maven-release-plugin] prepare release kryo-parent-5.0.1
• 8a724f1 [maven-release-plugin] rollback the release of kryo-parent-5.0.1
• c7ce6bd [maven-release-plugin] prepare release kryo-parent-5.0.1
• 94103dd #774 Do not re-use serializers for CompatibleFieldSerializer and TaggedFieldS...
• 04e0e90 Merge pull request #790 from theigl/789-stackoverflow-message
• 7cedf69 #789 Catch StackOverflowError and add hint for enabling references
• ae777c6 Merge pull request #787 from theigl/786-generics-depth
• ce54dec #786 Ensure field serializers balance pushGenericType and popGenericType ...
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #13.