Skip to content

chore: dependabot for security advisories only - #406

Open
pliablepixels wants to merge 1 commit into
mainfrom
chore/dependabot-security-only
Open

chore: dependabot for security advisories only#406
pliablepixels wants to merge 1 commit into
mainfrom
chore/dependabot-security-only

Conversation

@pliablepixels

Copy link
Copy Markdown
Member

Refs #392

Acceptance

Corrects how P9-2 was implemented in #394.

The finding said the audit backlog grew from 22 to 37 with no dependabot. True,
but I added routine version updates without first checking what the 37 were.
They are almost entirely @wdio/* and @capacitor/assets: device-test and
icon-generation tooling that never ships to a device. The first run opened five
PRs and fixed none of them.

Meanwhile the half that would have mattered was not running at all.
dependabot_security_updates and vulnerability alerts are repo settings, not
dependabot.yml, and both were disabled. So after #394 the repo had the churn
and none of the protection.

  • Vulnerability alerts: enabled.
  • Dependabot security updates: enabled.
  • Every version-update limit set to 0, which leaves security updates running
    and stops routine bumps.

Net effect: no scheduled PRs, and a PR when an advisory lands against something
that actually ships.

Checks run

  • .github/dependabot.yml parses; all three ecosystems at limit 0.
  • Repo settings verified after the change: dependabot_security_updates is
    enabled, vulnerability-alerts returns 204.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ug2KMTruP49Y8cmdZc97AW

The routine version-update half was churn. Its first run opened five PRs and
fixed none of the 37 audit findings, because those are almost entirely
@wdio/* and @capacitor/assets: device-test and icon-generation tooling that
never ships to a device.

The half that is worth interrupting for was not running at all. Dependabot
security updates and vulnerability alerts are repo settings rather than this
file, and both were disabled, so the audit backlog P9-2 flagged had nothing
watching it even after the config landed. Both are now on.

Every version-update limit goes to 0, which leaves security updates running
and stops the rest.

Refs #392 (P9-2, corrected)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ug2KMTruP49Y8cmdZc97AW
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