fix(zstd): vendor zstd v1.5.7 + deps batch (re-land) - #16
Merged
Conversation
nitro/nitrogen held at the peer-range ceiling (^0.35.0 -> 0.35.10); the coordinated 0.37 move across libs happens separately.
The previous pin (72c16b18) was an untagged zstd dev-branch commit, not the v1.5.6 tag .gitmodules claimed; now on the real v1.5.7 tag commit.
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
1 participant
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.
Re-lands PR #14, whose merge went into #15's branch instead of main (the two merges crossed before GitHub retargeted the stack) — so v1.3.3 shipped without these changes.
Same content as #14: dev-tooling batch (jest 30, prettier 3, commitlint 21, eslint 9.39.5, release-it 20 + plugin 11, nitro held at 0.35.10 peer ceiling) and
fix(zstd): vendor zstd v1.5.7(old pin was an untagged dev-branch commit). Merging auto-releases 1.3.4 with the real v1.5.7.