ci: bump google/osv-scanner-action/.github/workflows/osv-scanner-reusable-pr.yml from 3a7550f43ba5b58905a821ce3a0ed24c4858b3f4 to 9fd1bcce27f67e3bd819a0a7620e332803dc43bc - #426
Conversation
…able-pr.yml Bumps [google/osv-scanner-action/.github/workflows/osv-scanner-reusable-pr.yml](https://github.com/google/osv-scanner-action) from 3a7550f43ba5b58905a821ce3a0ed24c4858b3f4 to 9fd1bcce27f67e3bd819a0a7620e332803dc43bc. - [Release notes](https://github.com/google/osv-scanner-action/releases) - [Commits](google/osv-scanner-action@3a7550f...9fd1bcc) --- updated-dependencies: - dependency-name: google/osv-scanner-action/.github/workflows/osv-scanner-reusable-pr.yml dependency-version: 9fd1bcce27f67e3bd819a0a7620e332803dc43bc dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Warning Review limit reached
Next review available in: 33 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
seonghobae
left a comment
There was a problem hiding this comment.
Reviewed exact head 3a9c17a252cdb207839d49fd45fac214218dabf8. The PR changes only the SHA-pinned OSV reusable workflow reference. The upstream target 9fd1bcce27f67e3bd819a0a7620e332803dc43bc is the Google repository merge that adds GOTOOLCHAIN=auto to OSV scanner invocations while retaining the scanner action and container at immutable v2.3.8 SHAs. No permission expansion or mutable tag was introduced. Approved subject to a clean exact-head rebase onto the protected base and all required checks.
|
@coderabbitai review |
✅ Action performedReview finished.
|
seonghobae
left a comment
There was a problem hiding this comment.
Exact-head reusable-workflow review reconfirmed. The OSV Scanner reusable workflow is pinned to the reviewed immutable upstream commit containing the Go toolchain, permission, artifact pinning, and template-injection hardening. No actionable finding remains.
|
@coderabbitai review Protected commercial-readiness pass reconfirmed exact head |
|
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Pull request overview
OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.
Findings
1. HIGH Current-head GitHub Checks - Fix failed required checks before approval
- Problem: Failed same-head checks remain for
3a9c17a252cdb207839d49fd45fac214218dabf8. - Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
- Fix: Read and fix the failed check logs below, then rerun the current-head checks.
- Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.
Failed checks:
- Security Scan/trivy-fs: FAILURE (https://github.com/ContextualWisdomLab/scopeweave/actions/runs/30885409279/job/91915414277)
- Strix Security Scan/strix: FAILURE (https://github.com/ContextualWisdomLab/scopeweave/actions/runs/30885408431/job/91915412641)
- Strix Security Scan/strix: failure (https://github.com/ContextualWisdomLab/scopeweave/actions/runs/30885408431/job/91915412641)
- trivy-fs check run: failure (https://github.com/ContextualWisdomLab/scopeweave/actions/runs/30885409279/job/91915414277)
Changed-File Evidence Map
flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Workflow: osvscanner.yml"]
S1 --> I1["GitHub Actions review job"]
I1 --> R1["Review risk: Workflow: osvscanner.yml"]
R1 --> V1["actionlint plus required checks"]
OpenCode Review Overview
Pull request overviewOpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed. Findings1. HIGH Current-head GitHub Checks - Fix failed required checks before approval
Failed checks:
Changed-File Evidence Mapflowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Workflow: osvscanner.yml"]
S1 --> I1["GitHub Actions review job"]
I1 --> R1["Review risk: Workflow: osvscanner.yml"]
R1 --> V1["actionlint plus required checks"]
|
|
Superseded by #470. |
Bumps google/osv-scanner-action/.github/workflows/osv-scanner-reusable-pr.yml from 3a7550f43ba5b58905a821ce3a0ed24c4858b3f4 to 9fd1bcce27f67e3bd819a0a7620e332803dc43bc.
Commits
9fd1bccMerge pull request #138 from google/fix/gotoolchain-auto01a87d5fix: add GOTOOLCHAIN=auto env to osv-scanner callsa82132cMerge pull request #135 from google/fix-zizmor-excessive-permissions272ff57fix: address zizmor template injection warnings10621fbrefactor: move permissions to job level to satisfy zizmorfa4ff67Merge pull request #131 from BeyondEvil/feat/add-runs-on-inpute3f946afeat: add runs-on input to reusable workflowsb8ac13fMerge pull request #127 from SVilgelm/patch-105957d4Merge pull request #130 from google/gate-outputs-with-flag-20260519f6fb127Pin download-artifact action to SHADependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)