fix: pin zapdb v1.0.0 go.sum to proxy hash#4
Merged
Conversation
Same shape as the fhe v1.7.6 fix: local-direct git checkout produces different dirhash than proxy.golang.org (likely tag force-push or filtered content). sum.golang.org records the proxy hash; CI uses proxy and was failing checksum verification against the stale direct-hash recorded in go.sum. Pin the canonical proxy hashes (h1:u8TF4g... and h1:tT2WF2...).
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.
Same shape as the fhe v1.7.6 fix on luxfi/threshold — local-direct vs proxy-served dirhash disagree; CI uses proxy + sum.golang.org and was failing. Pin proxy hash.