This repository was archived by the owner on Apr 15, 2026. It is now read-only.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Inconsistent OSV Scanner version: scan-pr still pinned to v2.3.3 while scan-scheduled updated to v2.3.5
The PR updates the
scan-scheduledjob's commit hash toc51854704019a247608d928f370c98740469d4b5(v2.3.5) but leaves thescan-prjob atc5996e0193a3df57d695c1b8a1dec2a4c62e8730(v2.3.3) on line 21. Both jobs were previously pinned to the same v2.3.3 commit, indicating they should be kept in sync. This means PR scans will run a different (older) version of the scanner than push/scheduled scans, which could lead to inconsistent vulnerability detection results between the two jobs.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.