Repository navigation
Upgrade the bundled libzstd to 1.5.7 - #41
Merged
Merged
Conversation
The release build has compiled libzstd 1.5.5 since 2023; upstream has since shipped 1.5.6 (2024-03) and 1.5.7 (2025-02). Bump ZSTD_VERSION to 1.5.7 and ZSTD_SHA256 to the 1.5.7 release tarball's digest (verified against a fresh download from the facebook/zstd GitHub release), so the build keeps verifying the exact bytes it compiles. No other pin in the stack names a zstd version.
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.
The release build has compiled libzstd 1.5.5 since 2023. Upstream has since shipped 1.5.6 (March 2024) and 1.5.7 (February 2025) — two years of fixes the modernization pass didn't pick up, because the Dockerfile's version pin was the one dependency it didn't touch. This bumps ZSTD_VERSION to 1.5.7 and ZSTD_SHA256 to the new tarball's digest, verified against a fresh download from the facebook/zstd GitHub release, so the build keeps checking the exact bytes it compiles. Nothing else changes: the Dockerfile is the only place in the stack that names a zstd version.
Validated locally ahead of CI: the extension builds against 1.5.7 in the shipped configuration (whole-archive static link; the built library reports ZSTD_versionString() = 1.5.7), and its test results are identical to a baseline build against 1.5.5 — same passes, same failures, the failures being sandbox-environment gaps (missing htslib tools) present in both.