chore: remove a scan cache committed by mistake, and ignore the shape - #45
Merged
Conversation
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.
relcache/was committed in the v1.5.0 release PR. It is a scan cache from a manual run that was given an explicit path inside the working tree: a random salt and one cached finding set.No distribution impact. It sits outside every crate, so it was never in a published package, and the release archives carry built binaries only. It is junk in the source tree, and a committed cache is the exact shape the 1.4.0 and 1.5.0 work went to some trouble to make harmless.
Deleted, and
.gitignorenow covers a cache directory at the repository root so the next manual run cannot repeat it. Verified no tracked file is caught by the new patterns (git ls-files | git check-ignore --stdinreports nothing). No code change.