You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Digest: report Dependabot security updates off, and Dependabot PRs that did not merge #228
Part of the "apply every Dependabot update immediately" rollout (Andrew, 2026-10-25). After that change no human approves Dependabot PRs, so the digest is the only place that shows when the automatic path fails.
1. Dependabot security updates: on or off
scripts/dependabot-digest/standards.sh reads repos/{o}/{r}/vulnerability-alerts (dev-env#220). Alerts on does not mean security-update PRs open. STATUS.md (2026-10-21): on 7 NOS repos and vpn-lan-bridge, "Security updates were left off."
Read GET repos/{o}/{r}/automated-security-fixes (enabled, paused).
Check that the digest App installation has the permission this endpoint needs; record it in docs/runbooks/dependabot-digest-credentials.md if a scope change is necessary.
2. Dependabot PRs that did not merge
The digest buckets open Dependabot PRs by what a human must do. After github-workflows#203, every open Dependabot PR older than a few hours is a failure of the automatic path.
The paste-ready merge-lock lines stay for local use, but they are no longer the main path.
3. Run cadence
The digest runs at 14:00 UTC daily. With daily Dependabot schedules and immediate security PRs, decide whether that is enough, or whether the "not merged" check runs more often (the site-monitor launchd dispatch on MIMOLETTE is an option).
Tests: bash scripts/dependabot-digest/tests/run-tests.sh, with fixtures for each new state.
Linked to tracker #229, concern D. With the all-checks gate in github-workflows#203, a red main blocks every Dependabot PR, security fixes included. The "not merged" bucket must split "red on its own content" from "red because the default branch is red" (the #120amelia-boone case). The second needs a different owner and a different alert text, because the fix is in main, not in the PR.
Activity
twistedmelonman commentedon Oct 25, 2026
Linked to tracker #229, concern D. With the all-checks gate in github-workflows#203, a red
mainblocks every Dependabot PR, security fixes included. The "not merged" bucket must split "red on its own content" from "red because the default branch is red" (the #120amelia-boonecase). The second needs a different owner and a different alert text, because the fix is inmain, not in the PR.Generated by Claude Code