ci: pin ThreatCrush 0.6.2 - #3
Merged
Merged
Conversation
0.6.1 moved SARIF fingerprints to a content hash but kept publishing them under `primaryLocationLineHash`, which the CodeQL upload action computes itself — so the inconsistent-fingerprint warning stayed, once per finding, now comparing against the new hash. 0.6.2 publishes under `threatcrush/contentHash/v1` and leaves the reserved key to GitHub. Same hash, so finding identities carry over. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Clears the last of the SARIF upload warnings.
0.6.1 moved fingerprints to a content hash but kept publishing them under
primaryLocationLineHash. That key is computed by the CodeQL upload action itself, so it warned on every finding regardless of what we put there — the previous run logged it eight times, once per finding, comparing against the new hash:0.6.2 (profullstack/threatcrush#90) publishes under
threatcrush/contentHash/v1and leaves the reserved key to GitHub. The hash is unchanged, so existing finding identities carry over.Findings are unaffected: still the same 8, all genuine.