Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump com.esotericsoftware:kryo from 5.6.0 to 5.6.2 #3770

Merged
merged 3 commits into from
Nov 13, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 13, 2024

Bumps com.esotericsoftware:kryo from 5.6.0 to 5.6.2.

Release notes

Sourced from com.esotericsoftware:kryo's releases.

kryo-5.6.2

This is a maintenance release that recompiles 5.6.1 to restore compatibility with Java 8.

#1134 Recompile to ensure Java 8 support

Other Tasks:

  • Ensure release build can only happen with JDK 11

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.

Compatibility

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

kryo-5.6.1

DO NOT USE THIS VERSION

This version was accidentally targeted to Java 17. Use 5.6.2+ instead.


This is a maintenance release fixing wrong coordinates for the versioned artifact.

#1045 Re-add groupId to versioned POM

Other Tasks:

  • Fix deployment of snapshot builds
  • Upgrade Maven plugin dependencies

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.

Compatibility

  • Serialization compatible
    • Standard IO: Yes
    • Unsafe-based IO: Yes

... (truncated)

Commits
  • fee6387 [maven-release-plugin] prepare release kryo-parent-5.6.2
  • a7a6504 #1134 Ensure that JDK 11 is used to build the release artifacts
  • 6204b96 Bump junit.version from 5.11.1 to 5.11.2 (#1131)
  • 36b7555 Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.10.0 to 3.10.1 (#1133)
  • 29d9101 Bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.0 to 3.5.1 (#1132)
  • 3dca694 Update README for 5.6.1
  • 7261d15 Add compat report for 5.6.1
  • 3d4beb1 [maven-release-plugin] prepare for next development iteration
  • 7993436 [maven-release-plugin] prepare release kryo-parent-5.6.1
  • 0de506b Bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.6 to 3.2.7 (#1130)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Nov 13, 2024
@rzo1
Copy link
Contributor

rzo1 commented Nov 13, 2024

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 13, 2024

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

dependabot bot and others added 3 commits November 13, 2024 21:15
Bumps [com.esotericsoftware:kryo](https://github.com/EsotericSoftware/kryo) from 5.6.0 to 5.6.2.
- [Release notes](https://github.com/EsotericSoftware/kryo/releases)
- [Commits](EsotericSoftware/kryo@kryo-parent-5.6.0...kryo-parent-5.6.2)

---
updated-dependencies:
- dependency-name: com.esotericsoftware:kryo
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@rzo1 rzo1 force-pushed the dependabot/maven/com.esotericsoftware-kryo-5.6.2 branch from ecfbb49 to d919d37 Compare November 13, 2024 20:17
@rzo1 rzo1 merged commit f5bcdcc into master Nov 13, 2024
4 of 12 checks passed
@dependabot dependabot bot deleted the dependabot/maven/com.esotericsoftware-kryo-5.6.2 branch November 13, 2024 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant