Skip to content

ci(dependabot): let Dependabot bump the ci-workflows action pins - #193

Merged
kyle-sexton merged 2 commits into
mainfrom
ci/dependabot-first-party-actions
Nov 15, 2026
Merged

kyle-sexton merged 2 commits into
mainfrom
ci/dependabot-first-party-actions

Conversation

@kyle-sexton

Copy link
Copy Markdown
Member

No related issue: the first-party action pin work, tracked in the owner's audit session.

Summary

This repository's melodic-software/ci-workflows composite-action pins sat on v0.39.8 and on one untagged commit,
and Dependabot ignored every ci-workflows reference, so the pins moved only by hand. After this change Dependabot
keeps them on the newest release and the auto-merge caller merges that bump with nobody opening, marking ready or
merging a pull request.

Fix

  • .github/workflows/pr-require-checks.yml: the locally owned pins (lychee-offline, pr-require-checks/check-contract, pr-require-checks/aggregate-results) move to the v0.74.0 release commit
    944d346c487c79eaf85dff752586fb59b0f5c539, each with a # v0.74.0 comment.
  • .github/dependabot.yml, the github-actions entry: the ignore of melodic-software/ci-workflows/* becomes an
    ignore of the one pin in the sync-managed pr-check-managed-files-hosted.yml; first-party releases are excluded from the cooldown; a
    first-party-actions group moves every ci-workflows pin in one pull request.
  • .claude/ecosystems/cross-cutting.yaml: the record named the old pinned commit and line numbers inside the
    moved actions; it now points at the commits the workflow steps pin and at the actions' input names, so it stays
    true when Dependabot moves the pins. Its gitleaks citations are unchanged: that composite is not called here.

The reusable-workflow callers stay at @main. The auto-merge caller arms the bump from the synced Dependabot policy
copy (fastTrack.own), present here since #192.

Verification

  • This pull request's own CI Status runs the moved actions at v0.74.0.
  • standards components/dependabot-policy/dependabot-policy.mjs --root .: Dependabot policy passed.
  • aggregate-results is identical between its old pin and v0.74.0; the tool versions and checksums of the moved
    lint actions are unchanged at v0.74.0.
  • The same change is merged in agent-plugins (chore: sync standards components #143 there) and claude-code-account-rotation (#457 there).

Related

🤖 Generated with Claude Code

kyle-sexton and others added 2 commits November 15, 2026 13:33
The three locally owned ci-workflows action pins move to the v0.74.0 release
commit with a `# v0.74.0` comment. Dependabot then keeps them current: the
blanket ignore of melodic-software/ci-workflows becomes an ignore of the one
pin in the sync-managed file, first-party releases skip the cooldown, and
they move together in a `first-party-actions` group that the auto-merge
caller arms from the synced Dependabot policy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The cross-cutting record named ci-workflows@594987a (v0.39.8) and line
numbers in the lychee-offline action for pins this change moved, and that
Dependabot now moves at each release. It points at the commit the workflow
step pins and at the action's input defaults by name. The gitleaks
citations stay: that composite is not called here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-15T18:59:49.008050Z 2809a11 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

Copy link
Copy Markdown

claude-review reviewed 2809a112e931913020591a3e498182ae281d4966: 0 finding(s), 0 as inline comments.

No findings on this PR; I did not run the code or check the upstream pins, so parts of the review rest on the author's claims.

I read the full diff (3 files) and the PR context. There is no closing issue ("No related issue"), so I checked no acceptance criteria. There are no plugin manifest changes, so no manifest <field> lines apply.

What I checked at the PR head

  • Pins: the three ci-workflows pins in pr-require-checks.yml (lines 104, 131 and 139) now use the same commit, 944d346c, each with a # v0.74.0 comment. The check-managed-files pin stays at v0.71.0 in the sync-managed pr-check-managed-files-hosted.yml:118.
  • dependabot.yml: the ignore entry now names only melodic-software/ci-workflows/.github/actions/check-managed-files, which is the one first-party pin in .github/ that isn't bumped here. The first-party-actions group sits before vendor-actions and github-actions, so first-party pins group first. The cooldown exclude is consistent with the new header comment.
  • cross-cutting.yaml: the rewritten header and notes now point at the pr-require-checks.yml:104 pin and at the action's input names instead of old line numbers, so they won't go stale when Dependabot moves the pins. The pr-require-checks.yml line references it still cites (:93-106, :104-106, :130-133, :134-153, :108) were not re-verified against the new file. The gitleaks citations at ci-workflows@594987a remain accurate because that composite is not called here.

Not verified

  • That the lychee tool-pin and checksum are unchanged at v0.74.0. I tried to read the upstream action file with gh api, but that call needed an approval I didn't have. That claim, and the author's statement that aggregate-results is identical between the old pin and v0.74.0, are author-claimed and unverified.
  • That Dependabot treats the full subdirectory path melodic-software/ci-workflows/.github/actions/check-managed-files as the dependency name for the ignore entry. This is my expectation of Dependabot's naming, not something I tested.

Verifier dropped 0 of 0 candidates.

@github-actions

Copy link
Copy Markdown

claude-security-review reviewed 2809a112e931913020591a3e498182ae281d4966: 0 finding(s), 0 as inline comments.

Security review: PR #193, no findings

Changes reviewed

  • .github/workflows/pr-require-checks.yml moves three melodic-software/ci-workflows composite-action pins to 944d346c487c79eaf85dff752586fb59b0f5c539 (commented v0.74.0):
    • lychee-offline was 594987a (v0.39.8).
    • check-contract was 594987a (v0.39.8).
    • aggregate-results was ac4d878.
    • All three remain full-SHA pins.
  • .github/dependabot.yml adds a first-party-actions group matching melodic-software/* and exempts melodic-software/ci-workflows/* from the 3-day cooldown. The ignore rule narrows to the sync-managed check-managed-files pin.
  • .claude/ecosystems/cross-cutting.yaml changes comments and a notes string only.

Analysis

  • The diff does not change which pull requests get auto-merged. The allowlist lives in the pr-automerge-dependabot.yml@main reusable in ci-workflows. The caller (.github/workflows/pr-automerge-dependabot.yml, unchanged) still describes actions/*, github/* and anthropics/* only.
  • The new comment in dependabot.yml says first-party-actions is an auto-merge lane. That is true only if the remote reusable allows it, and the diff does not show that.
  • The group and the dropped cooldown cover first-party publisher code only. The owner threat model treats the owner's own repositories and actions as the trusted actors. A merge still needs CI Status to pass. There is no untrusted-input path, so I rate this neither CRITICAL nor IMPORTANT.
  • With no soak time on first-party bumps, the SHA pin in each bump is the main supply-chain control. Reviewers should check that the SHA matches the tagged release.

Not checked

  • I could not confirm that 944d346… is the commit behind tag v0.74.0. The gh api call needed approval and was not run. Nothing in the repository contradicts the pin.
  • No plugin or marketplace manifest fields are touched.
  • The instruction-surface lens does not apply.

critical-findings: 0

@kyle-sexton
kyle-sexton merged commit 84e1f8f into main Nov 15, 2026
8 checks passed
@kyle-sexton
kyle-sexton deleted the ci/dependabot-first-party-actions branch November 15, 2026 18:58
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