Skip to content

v1.0.2 — fix Dependabot-report bot-actor block (+ marker wording) - #3

Merged
mcarter-astronautdev merged 1 commit into
mainfrom
fix/dependabot-report-allowed-bots
Jun 17, 2026
Merged

v1.0.2 — fix Dependabot-report bot-actor block (+ marker wording)#3
mcarter-astronautdev merged 1 commit into
mainfrom
fix/dependabot-report-allowed-bots

Conversation

@mcarter-astronautdev

Copy link
Copy Markdown
Member

Fixes the Dependabot-report leg, which silently failed on real Dependabot PRs (pilot #50/#51): validate ran green but no verdict + no reviewer.

Root cause

dependabot-report runs on a workflow_run triggered by Dependabot's validate run → initiating actor is dependabot[bot]claude-code-action blocks bot initiators (Workflow initiated by non-human actor) → verdict step fails → post-verdict + reviewer-request skipped.

Fix

  • allowed_bots: "dependabot[bot]" on the report's claude step. Safe: that step only READS the inert artifact (Read/Glob/Grep/Write — no gh, shell, or execution), so a bot initiating it doesn't widen the trust surface.
  • continue-on-error on that step + always() on the resolve/post steps, so a verdict-generation hiccup still pings a human with the bare conclusion (the job's documented intent — previously a claude failure skipped the ping).
  • Marker wording (queued v1.0.2 — batched refinements (start: PR-first marker wording) #2): "findings, if any, are inline above."

Ships as v1.0.2. Consumers repin via PRs driver-bonsai-mcp#3 + vite-plugin-shopify-clean#49; then pilot #50/#51 get re-triggered.

dependabot-report runs on a workflow_run triggered by Dependabot's validate run,
so the initiating actor is dependabot[bot]. claude-code-action refuses bot
initiators unless allow-listed, so the 'reason over build result' step failed
and the verdict + reviewer-request never posted (validate was green but the PR
went silently un-reviewed — observed on pilot PRs #50/#51).

- allowed_bots: "dependabot[bot]" on the report's claude step (safe: it only
  READS the inert artifact with a Read/Glob/Grep/Write tool surface — no gh,
  shell, or execution).
- continue-on-error on that step + always() on resolve/post so a verdict-gen
  hiccup still pings a human (the job's documented intent).
- pr-first marker wording: 'findings, if any, are inline above' (queued #2).
@mcarter-astronautdev
mcarter-astronautdev merged commit bfcafe2 into main Jun 17, 2026
mcarter-astronautdev added a commit that referenced this pull request Jun 17, 2026
A blocked Dependabot PR we couldn't act on (gh pr comment failed, or its
mergeStateStatus never resolved out of UNKNOWN after retries) was previously a
silent green run. Track failures and exit non-zero so it's a visible red run.
One bad PR no longer suppresses the others. (Code-review finding on PR #3.)
set -e behavior verified locally across 6 scenarios.
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