Skip to content

Skip dependency review when dependency graph is unavailable#341

Merged
seonghobae merged 1 commit into
mainfrom
agent/dependency-review-preflight
Jul 7, 2026
Merged

Skip dependency review when dependency graph is unavailable#341
seonghobae merged 1 commit into
mainfrom
agent/dependency-review-preflight

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

  • preflight the dependency graph compare API before running dependency-review-action
  • skip the dependency-review hard gate only when GitHub reports dependency graph support is unavailable for the repository
  • keep high-severity dependency findings hard-failing when the dependency graph API is available

Verification

  • uv run --python 3.13 pytest -s -q tests/test_required_workflow_queue_contract.py
  • parsed .github/workflows/security-scan.yml with PyYAML
  • observed seedream_evasepic Security Scan failure: dependency-review-action reported dependency graph is not supported on that repository

@seonghobae seonghobae merged commit 2fd9879 into main Jul 7, 2026
0 of 12 checks passed
@seonghobae seonghobae deleted the agent/dependency-review-preflight branch July 7, 2026 06:14

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was cancelled, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was cancelled, so required test/docstring evidence was not proven for current head e8a4404dd3715e7190617e2a54b76d2c166c0f1d.

  • Head SHA: e8a4404dd3715e7190617e2a54b76d2c166c0f1d

  • Workflow run: 28845644650

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: security-scan.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: security-scan.yml"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Test: test_required_workflow_queue_contract.py"]
  S2 --> I2["regression suite"]
  I2 --> R2["Review risk: Test: test_required_workflow_queue_contract.py"]
  R2 --> V2["targeted test run"]
Loading

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: e8a4404dd3715e7190617e2a54b76d2c166c0f1d
  • Workflow run: 28845644650
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was cancelled, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was cancelled, so required test/docstring evidence was not proven for current head e8a4404dd3715e7190617e2a54b76d2c166c0f1d.

  • Head SHA: e8a4404dd3715e7190617e2a54b76d2c166c0f1d

  • Workflow run: 28845644650

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: security-scan.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: security-scan.yml"]
  R1 --> V1["actionlint plus required checks"]
  Evidence --> S2["Test: test_required_workflow_queue_contract.py"]
  S2 --> I2["regression suite"]
  I2 --> R2["Review risk: Test: test_required_workflow_queue_contract.py"]
  R2 --> V2["targeted test run"]
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant