Scan with osv-scanner v2.5.1 - #80
Merged
Merged
Conversation
The scanner version rides a download URL, so dependabot never sees it and it only moves by hand. Nine repos sat on v2.4.0 while the fleet template had already moved to v2.5.1, so half the workspace was being scanned by an older scanner than the other half and nothing said so. Verified the v2.5.1 release carries both asset names our workflows fetch (osv-scanner_linux_amd64 and _arm64) before changing the URL, since a renamed asset would have broken every one of these jobs at once. Co-Authored-By: Claude Opus 5 (1M context) <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.
Summary
Moves the osv-scanner binary this repo downloads from v2.4.0 to v2.5.1.
The scanner version rides a download URL rather than an action tag, so dependabot never sees it and it only moves by hand. Nine repos sat on v2.4.0 while the fleet template had already moved to v2.5.1: half the workspace was being scanned by an older scanner than the other half, with nothing reporting the split.
Verified the v2.5.1 release carries both asset names our workflows fetch (
osv-scanner_linux_amd64andosv-scanner_linux_arm64) before changing the URL, since a renamed asset would have broken every one of these jobs at once.Type of change
Public API
None. CI tooling only.
Test plan
The security workflow is its own gate: it runs the scanner on this PR. Asset names confirmed against the upstream release before the change.
Checklist