build.zig.zon: Fix package hashes for Zig 0.14#4301
Merged
clason merged 1 commit intotree-sitter:masterfrom Mar 21, 2025
Merged
build.zig.zon: Fix package hashes for Zig 0.14#4301clason merged 1 commit intotree-sitter:masterfrom
clason merged 1 commit intotree-sitter:masterfrom
Conversation
Zig 0.14 changed how package hashes are computed and used, and if the old package hashes are left, every call to `zig build` will re-download every package every time. Updating to the new hash format solves this.
clason
approved these changes
Mar 21, 2025
Contributor
|
Thanks! |
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
2 participants
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.
Summary
Zig 0.14 changed how package hashes are computed and used, and if the old package hashes are left, every call to
zig buildwill re-download every dependency every time (this also occurs with downstream packages that include tree-sitter in theirbuild.zig.zon). Updating to the new hash format solves this.Verification
To verify each package hash for yourself (as once a package is downloaded only the hash will be used to reference it), you can use the
zig fetchcommand:After downloading the tarball it will compute and print the package hash.