fix: preserve historical snapshot fingerprints#99
Merged
Conversation
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: fix: preserve historical snapshot fingerprints This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
Collaborator
Author
|
Landed in 05ae103. Proof on exact PR head
No release, tag, or publish action was performed. |
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.
Summary
Proof
go test -count=1 ./...(85.0% aggregate coverage)go test -race -count=1 ./...golangci-lint,go vet,staticcheck,deadcode,gofumptgosec,govulncheck,gitleaksdoctor,status, and private-safe archive searchFollow-up to #98 after its concurrent merge. This addresses the historical-manifest finding from the review on that PR.