Skip to content

chore: track pinned action SHAs with a dependabot config - #255

Merged
randomparity merged 3 commits into
mainfrom
feat/add-dependabot-config-236
Aug 26, 2026
Merged

chore: track pinned action SHAs with a dependabot config#255
randomparity merged 3 commits into
mainfrom
feat/add-dependabot-config-236

Conversation

@randomparity

Copy link
Copy Markdown
Owner

Closes #236

The repository pins four GitHub Actions by full SHA across its two workflows —
actions/checkout v7.0.1, actions/upload-pages-artifact v5.0.0,
actions/deploy-pages v5.0.0 and actions/setup-node v7.0.0 — and nothing
watched them. There was no .github/dependabot.yml at all, so a pinned SHA
going stale, or an upstream advisory against a pinned revision, would have been
noticed only by someone reading the workflow files by hand.

What this adds

One updates entry for github-actions at directory: "/".

That is the complete set. This repository has no package.json, Cargo.toml,
pyproject.toml or requirements.txt, so github-actions is the only
ecosystem present and a second entry would describe nothing.

The shape is not invented here

$restock already specifies what a dependabot.yml in this repository must
satisfy — skills/restock/SKILL.md:168-214, under
docs/adr/0012-restock-composes-shared-workflow-contracts.md (Accepted
2026-08-13). It verifies five conditions and carries the per-entry template
verbatim. This file meets all five:

condition met by
every detected ecosystem covered the single github-actions entry
uv not pip where both pyproject.toml and uv.lock exist not applicable — neither file exists
schedule.interval: "weekly" present
cooldown.default-days: 7 present
groups with patterns: ["*"] github-actions-dependencies

The cooldown is the condition worth naming: without it, dependabot re-opens
rapidly after a pull request is closed or merged, and the queue fills with
re-attempts.

$restock also prescribes a branch name, a commit message and its own
gh pr create invocation. Those belong to its standalone flow and are
deliberately not followed here — this change came through $quest, whose
branch convention governs. Only the five conditions and the entry template were
taken.

Verification

just verify run bare, exit 0, including just actions-check (actionlint and
zizmor) and just plugin-check. The managed pre-push hook re-ran the whole
suite in its isolated worktree on push, green.

The base-branch workflow runs this merge would trigger are not covered by that
evidence. Whether dependabot then opens sensible pull requests is likewise
unverified here — that is observable only after the first scheduled run.

No automated process tracked the repository's SHA-pinned GitHub Actions.
Add .github/dependabot.yml covering the sole detected ecosystem
(github-actions) with a weekly schedule, a 7-day cooldown, and grouped
updates, per the shape $restock's audit expects (skills/restock/SKILL.md,
backed by ADR 0012).

Bump the plugin version per ADR 0022.

Fixes #236
…onfig-236

# Conflicts:
#	.claude-plugin/plugin.json
…onfig-236

# Conflicts:
#	.claude-plugin/plugin.json
@randomparity
randomparity merged commit ddc5e1d into main Aug 26, 2026
5 checks passed
@randomparity
randomparity deleted the feat/add-dependabot-config-236 branch August 26, 2026 15:36
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.

No dependabot.yml, so the repository's pinned action SHAs are tracked by nobody

1 participant