Repository navigation
[fix][sec] Upgrade zstd-jni to 1.5.7-20 - #26766
Merged
Merged
Conversation
Assisted-by: Codex
lhotari
requested review from
Technoboy-,
dao-jun,
david-streamlio,
merlimat and
nodece
September 29, 2026 20:29
merlimat
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Update zstd-jni beyond 1.5.7-15 to include upstream maintenance fixes. Pulsar directly uses this dependency in compression interoperability tests; its production ZSTD codec uses Airlift.
Modifications
Upgrade zstd-jni from 1.5.7-15 to 1.5.7-20. The new release is a multi-release jar: Java 17/21 retain JNI implementations, while Java 22+ can select the FFM implementations provided by the library.
Verifying this change
help assemble sanityCheck checkBinaryLicensepassed with configuration cache enabled, including Checkstyle/Spotless. All 51 cases in CompressorCodecBackwardCompatTest and CompressorCodecTest passed on both Java 17 and Java 25 with retries disabled and no skips. These cover Pulsar's codec interoperability; they are not exhaustive coverage of the library's new FFM APIs.Does this pull request potentially affect one of the following parts: