dependabot[bot] opened a new pull request, #4539:
URL: https://github.com/apache/ignite-3/pull/4539

   Bumps [com.esotericsoftware:kryo](https://github.com/EsotericSoftware/kryo) 
from 5.6.0 to 5.6.2.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/EsotericSoftware/kryo/releases";>com.esotericsoftware:kryo's
 releases</a>.</em></p>
   <blockquote>
   <h2>kryo-5.6.2</h2>
   <p>This is a maintenance release that recompiles 5.6.1 to restore 
compatibility with Java 8.</p>
   <p><a 
href="https://redirect.github.com/EsotericSoftware/kryo/issues/1134";>#1134</a> 
Recompile to ensure Java 8 support</p>
   <p>Other Tasks:</p>
   <ul>
   <li>Ensure release build can only happen with JDK 11</li>
   </ul>
   <p>The full list of changes can be found <a 
href="https://github.com/EsotericSoftware/kryo/compare/kryo-parent-5.6.1...kryo-parent-5.6.2";>here</a>.</p>
   <p>Many thanks to all contributors!</p>
   <h2>Upgrade Notes</h2>
   <p>For migration from previous major versions please check out the <a 
href="https://github.com/EsotericSoftware/kryo/wiki/Migration-to-v5";>migration 
guide</a>. 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.</p>
   <h3>Compatibility</h3>
   <ul>
   <li>Serialization compatible
   <ul>
   <li>Standard IO: Yes</li>
   <li>Unsafe-based IO: Yes</li>
   </ul>
   </li>
   <li>Binary compatible - Yes (<a 
href="https://rawgithub.com/EsotericSoftware/kryo/master/compat_reports/kryo/5.6.1_to_5.6.2/compat_report.html";>Details</a>)</li>
   <li>Source compatible - Yes (<a 
href="https://rawgithub.com/EsotericSoftware/kryo/master/compat_reports/kryo/5.6.1_to_5.6.2/compat_report.html#Source";>Details</a>)</li>
   </ul>
   <h2>kryo-5.6.1</h2>
   <h2>DO NOT USE THIS VERSION</h2>
   <p>This version was accidentally targeted to Java 17. Use 5.6.2+ instead.</p>
   <hr />
   <p>This is a maintenance release fixing wrong coordinates for the versioned 
artifact.</p>
   <p><a 
href="https://redirect.github.com/EsotericSoftware/kryo/issues/1045";>#1045</a> 
Re-add groupId to versioned POM</p>
   <p>Other Tasks:</p>
   <ul>
   <li>Fix deployment of snapshot builds</li>
   <li>Upgrade Maven plugin dependencies</li>
   </ul>
   <p>The full list of changes can be found <a 
href="https://github.com/EsotericSoftware/kryo/compare/kryo-parent-5.6.0...kryo-parent-5.6.1";>here</a>.</p>
   <p>Many thanks to all contributors!</p>
   <h2>Upgrade Notes</h2>
   <p>For migration from previous major versions please check out the <a 
href="https://github.com/EsotericSoftware/kryo/wiki/Migration-to-v5";>migration 
guide</a>. 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.</p>
   <h3>Compatibility</h3>
   <ul>
   <li>Serialization compatible
   <ul>
   <li>Standard IO: Yes</li>
   <li>Unsafe-based IO: Yes</li>
   </ul>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/fee63879ddcec23fbd09ac7785bc04a3de758483";><code>fee6387</code></a>
 [maven-release-plugin] prepare release kryo-parent-5.6.2</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/a7a6504303107f6b2ad453c53048e901e8f885a8";><code>a7a6504</code></a>
 <a 
href="https://redirect.github.com/EsotericSoftware/kryo/issues/1134";>#1134</a> 
Ensure that JDK 11 is used to build the release artifacts</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/6204b9678e9d443f771ff37f657d9067cbdd84d7";><code>6204b96</code></a>
 Bump junit.version from 5.11.1 to 5.11.2 (<a 
href="https://redirect.github.com/EsotericSoftware/kryo/issues/1131";>#1131</a>)</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/36b7555fbe668d6f7fb4996b3823ca0c6decc3de";><code>36b7555</code></a>
 Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.10.0 to 3.10.1 (<a 
href="https://redirect.github.com/EsotericSoftware/kryo/issues/1133";>#1133</a>)</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/29d9101e67877a35d63e5afeaaf6b4dd268331b0";><code>29d9101</code></a>
 Bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.0 to 3.5.1 (<a 
href="https://redirect.github.com/EsotericSoftware/kryo/issues/1132";>#1132</a>)</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/3dca694a69d0ab950f478e11bfbf2e22670c2502";><code>3dca694</code></a>
 Update README for 5.6.1</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/7261d156e77e14b4fed4093348d01c2ca99b4fb6";><code>7261d15</code></a>
 Add compat report for 5.6.1</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/3d4beb1b6086398c13c5a0e0b9402d8a17260c35";><code>3d4beb1</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/799343664b777e3ddd365177e739830d63631408";><code>7993436</code></a>
 [maven-release-plugin] prepare release kryo-parent-5.6.1</li>
   <li><a 
href="https://github.com/EsotericSoftware/kryo/commit/0de506b86c492069a2e5fa8cf2ec1f309eec43c2";><code>0de506b</code></a>
 Bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.6 to 3.2.7 (<a 
href="https://redirect.github.com/EsotericSoftware/kryo/issues/1130";>#1130</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/EsotericSoftware/kryo/compare/kryo-parent-5.6.0...kryo-parent-5.6.2";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.esotericsoftware:kryo&package-manager=gradle&previous-version=5.6.0&new-version=5.6.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@ignite.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to