renovate-bot opened a new pull request, #7284:
URL: https://github.com/apache/texera/pull/7284

   This PR contains the following updates:
   
   | Package | Update | Change |
   |---|---|---|
   | 
[io.altoo:pekko-kryo-serialization](https://redirect.github.com/altoo-ag/pekko-kryo-serialization)
 | minor | `1.3.0` → `1.5.1` |
   
   ---
   
   > [!WARNING]
   > Some dependencies could not be looked up. Check the [Dependency 
Dashboard](../issues/6912) for more information.
   
   ---
   
   ### Release Notes
   
   <details>
   <summary>altoo-ag/pekko-kryo-serialization 
(io.altoo:pekko-kryo-serialization)</summary>
   
   ### 
[`v1.5.1`](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/releases/tag/v1.5.1)
   
   [Compare 
Source](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/compare/v1.5.0...v1.5.1)
   
   #### What's Changed
   
   - Use the new threadlocal based serializer-cache for pekko.
   
   **Full Changelog**: 
<https://github.com/altoo-ag/pekko-kryo-serialization/compare/v1.5.0...v1.5.1>
   
   ### 
[`v1.5.0`](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/releases/tag/v1.5.0)
   
   [Compare 
Source](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/compare/v1.4.0...v1.5.0)
   
   #### What's Changed
   
   - Drop scala 2.12 and jdk 11 support since upstream pekko 2.x also drops 
these
   - Tested against pekko 2.x as well as pekko 1.x
   - Several performance optimizations in concurrency, collection 
deserialization and ByteString see benchmark.md
   
   **Full Changelog**: 
<https://github.com/altoo-ag/pekko-kryo-serialization/compare/v1.4.0...v1.5.0>
   
   ### 
[`v1.4.0`](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/releases/tag/v1.4.0)
   
   [Compare 
Source](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/compare/v1.3.2...v1.4.0)
   
   #### What's Changed
   
   - Upgrade dependencies and make compatible to pekko 2.x
   - Updated documentation
   
   **Full Changelog**: 
<https://github.com/altoo-ag/pekko-kryo-serialization/compare/v1.3.2...v1.4.0>
   
   ### 
[`v1.3.2`](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/releases/tag/v1.3.2)
   
   [Compare 
Source](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/compare/v1.3.1...v1.3.2)
   
   #### What's Changed
   
   - No functional change
   - upgraded scala versions
   - added tests for jdk 25 and pekko 1.4.0 (additional to 1.1.5)
   
   **Full Changelog**: 
<https://github.com/altoo-ag/pekko-kryo-serialization/compare/v1.3.1...v1.3.2>
   
   ### 
[`v1.3.1`](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/releases/tag/v1.3.1)
   
   [Compare 
Source](https://redirect.github.com/altoo-ag/pekko-kryo-serialization/compare/v1.3.0...v1.3.1)
   
   #### What's Changed
   
   - fix lz4 
[cve-2025-12183](https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-12183)
 by using the latest lz4 library (upgrade scala-kryo-serialization)
   - update documentation
   
   **Full Changelog**: 
<https://github.com/altoo-ag/pekko-kryo-serialization/compare/v1.3.0...v1.3.1>
   
   </details>
   
   ---
   
   ### Configuration
   
   📅 **Schedule**: (in timezone Etc/UTC)
   
   - Branch creation
     - "before 8am on monday"
   - Automerge
     - At any time (no schedule defined)
   
   🚦 **Automerge**: Disabled by config. Please merge this manually once you are 
satisfied.
   
   ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry 
checkbox.
   
   🔕 **Ignore**: Close this PR and you won't be reminded about this update 
again.
   
   ---
   
    - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR was generated by [Mend Renovate](https://mend.io/renovate/). View 
the [repository job log](https://developer.mend.io/github/apache/texera).
   
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4zLjIiLCJ1cGRhdGVkSW5WZXIiOiI0NC4zLjIiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImRlcGVuZGVuY2llcyJdfQ==-->
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to