Pin the deduplicated zig-hdc - #714
Merged
Merged
Conversation
gHashTag/zig-hdc#3 made its duplicated src/vsa/* files re-export one repaired implementation, and its CI is green with the whole public surface analysed. The pin here predates that, so this build was still consuming the copies that carry the five API-drift errors.
gHashTag
force-pushed
the
fix/repin-zig-hdc
branch
from
August 11, 2026 19:06
df41b65 to
94075d4
Compare
zig-hdc pins the repaired golden-float and this one still pinned the archive from before those sixteen defects were fixed, so the fetch reported a hash mismatch rather than a compile error. Both manifests name the same archive now.
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.
gHashTag/zig-hdc#3 made its duplicated
src/vsa/*re-export one repaired implementation, and its CI is green with the whole public surface analysed. The pin here predates that, so this build was still consuming the copies carrying the five API-drift errors.