Skip to content

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

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

@kyle-sexton kyle-sexton commented Nov 15, 2026 •

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 three 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. The aggregate-results pin carried
    a short-SHA comment, which the runner-policy pin-provenance-drift check ties to the pinned commit; a release tag
    comment is what Dependabot rewrites.
  • .github/dependabot.yml: 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.

The reusable-workflow callers stay at @main; Dependabot does not rewrite a branch reference. The ignore's stated
reason, a lockstep for pinned reusable callers, ended when those callers moved to @main (standards runner-policy
README, "Contract revision lockstep").

The auto-merge caller arms the bump from the synced Dependabot policy copy (fastTrack.own), present here since
agent-plugins#142.

Verification

  • This pull request's own CI Status runs the three actions at v0.74.0.
  • standards components/dependabot-policy/dependabot-policy.mjs --root .: Dependabot policy passed.
  • provisioning runs the same configuration: provisioning#1031, a first-party bump, merged by itself.

Local check record

.claude/ecosystems/cross-cutting.yaml named ci-workflows@594987a (v0.39.8) and line numbers in the
lychee-offline action for the moved pins. It now points at the commit pr-require-checks.yml:119 pins and at the
action's input defaults by name, so it stays true when Dependabot moves the pin. The lychee version and checksum
defaults are the same at v0.74.0 (0.24.2). Its gitleaks citations are unchanged: that composite is not called here.

Related

  • provisioning#1028, standards#1026, standards#1025, ci-workflows#1101

🤖 Generated with Claude Code

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 Fable 5.2 <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:26:05.869497Z 6f1485b 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

github-actions Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

claude-review reviewed 66b8561e9b5d42c8deb320d2406a5f5b0529d03a: 0 finding(s), 0 as inline comments.

Incremental review of .claude/ecosystems/cross-cutting.yaml (since 6f1485b): no findings.

The change drops the lychee-offline/action.yml line-number citations at the old 594987a (v0.39.8) pin. The header comment and notes now describe the lychee command, version and checksum as the action's input defaults at whatever commit pr-require-checks.yml:119 pins. They also tell the reader to compare tool-pin with those defaults when a Dependabot bump merges. This closes the drift the PR body listed under "Not changed".

Checked against the workflow at head:

  • The remaining pr-require-checks.yml line citations match. The jq calls are at :105-106, the lychee uses at :119 and its config: at :121, and the check-contract and aggregate-results pins at :148 and :156.
  • The new wording that check-contract and aggregate-results sit at the same commit matches the workflow, where both are at 944d346… (v0.74.0). The old aggregate-results@ac4d878 citation is removed, so the notes no longer contradict the file.
  • The remaining 594987a (v0.39.8) mentions are the gitleaks composite, which this repository does not call, so the old pin is the correct reference there.

Not verified: the notes now name the action's globs, config, exclude, version and sha256 inputs. The sandbox denied reading lychee-offline/action.yml at v0.74.0, so I could not confirm those input names. The PR body's claim that the lychee version and checksum are unchanged at v0.74.0 is the author's and also unchecked by me. These are documentation strings that do not affect check-cmd, so I am not reporting them as findings.

Method notes:

  • The checked-out working tree still held the pre-change text of this file, so I judged the change from .claude-lane/incremental.diff.
  • I could not read the head blob with git show because the sandbox denied it.
  • No manifests changed, so there are no manifest lines.
  • The PR context names no closing issue, only "No related issue", so there are no acceptance criteria to check.
  • No security items are in this diff.
  • No subagents were used.

Verifier dropped 0 of 0 candidates.

@github-actions

github-actions Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

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

No security findings in the incremental change to .claude/ecosystems/cross-cutting.yaml (6f1485b → 66b8561).

  • Scope: the diff touches only the header comment and the notes: string. check-cmd, tool-pin (lychee 0.24.2, gitleaks 8.30.1) and gates: [] are unchanged.
  • What changed: the lychee composite is no longer described as pinned at ci-workflows@594987a. It is now described as the commit pr-require-checks.yml:119 pins, which Dependabot moves to each ci-workflows release. The notes point to the action's input defaults instead of fixed line numbers, and the check-contract and aggregate-results references now say "at the commit it pins". The gitleaks composite reference stays at ci-workflows@594987a (v0.39.8).
  • Instruction surface: no rule, hook allowlist, permission or validator is removed or softened. The notes are descriptive documentation of local lint parity with CI, not a standing instruction. No imperative text aimed at the model appears in the change. I did not consult the instruction exception register, because nothing in the diff removes a rule.
  • Trust controls: none are touched (trusted-actor list, token scope, kill switch, merge holds, .github/actions/). There is no manifest or userConfig change.
  • Supply chain: the notes describe a pin moving with Dependabot, but this change edits only prose in a lint record. It changes no pin, workflow or permissions: block. Pin hardening is zizmor's lane, so it is not re-reported here.

Skip gate 2 applies: there is no security-relevant surface.

critical-findings: 0

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 Fable 5.2 <noreply@anthropic.com>
@kyle-sexton
kyle-sexton merged commit e5e26cd into main Nov 15, 2026
11 checks passed
@kyle-sexton
kyle-sexton deleted the ci/dependabot-first-party-actions branch November 15, 2026 18:32
kyle-sexton added a commit to melodic-software/claude-code-account-rotation that referenced this pull request Nov 15, 2026
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 three 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. The
  `dotnet-sdk` and `nuget` entries are unchanged.

The reusable-workflow callers stay at `@main`. The ignore's stated
reason, a lockstep for pinned reusable callers,
ended when those callers moved to `@main` (standards runner-policy
README, "Contract revision lockstep"). The
auto-merge caller arms the bump from the synced Dependabot policy copy
(`fastTrack.own`), present here since #456.

## Verification

- This pull request's own `CI Status` runs the three actions at v0.74.0.
- standards `components/dependabot-policy/dependabot-policy.mjs --root
.`: `Dependabot policy passed.`
- No file outside `.github/workflows` names the moved pins; the synced
runner-policy copy lists reusable-workflow
  commits only.
- The same change is merged in agent-plugins (#143 there) and
provisioning (#1028, #1031 there).

## Related

- melodic-software/agent-plugins#143, melodic-software/standards#1026

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
kyle-sexton added a commit to melodic-software/cursor-plugins that referenced this pull request Nov 15, 2026
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`, `typos`, `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 #161.

## 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 (#143 there) and
claude-code-account-rotation (#457 there).

## Related

- melodic-software/agent-plugins#143, melodic-software/standards#1026

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
kyle-sexton added a commit to melodic-software/codex-plugins that referenced this pull request Nov 15, 2026
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 (#143 there) and
claude-code-account-rotation (#457 there).

## Related

- melodic-software/agent-plugins#143, melodic-software/standards#1026

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
kyle-sexton added a commit to melodic-software/ci-runner that referenced this pull request Nov 15, 2026
No related issue: the first-party action pin work, tracked in the
owner's audit session.

## Summary

Dependabot ignored this repository's `melodic-software/ci-workflows`
action pins, and `release/dependencies.json`
held a second copy of the pinned commit that every bump had to edit by
hand. After this change the workflow `uses:`
lines are the only record of that pin, as they already are for every
other Action, Dependabot keeps the pins on the
newest ci-workflows release, and the auto-merge caller merges that bump
with no manual edit.

## Fix

Tooling (first commit, green with the pins still on v0.73.0):

- `release/dependencies.json`: the `melodic-software/ci-workflows` entry
leaves `repositoryPins` (now `[]`).
- `scripts/ReleasePinSources.ps1` (`Get-WorkflowActionPins`):
ci-workflows composite actions are read like every other
Action, so every use must name one commit and one `# vX.Y.Z` release.
Two ci-workflows references are skipped: a
reusable workflow called at `@main`, and the pin in a `SYNC-MANAGED
FILE`.
- `scripts/Test-DependencyFreshness.ps1`: one expression made safe for
an empty `repositoryPins` under StrictMode.
- `.github/scripts/workflow-pin-metadata.test.cjs`: the
manifest-agreement test is removed; the caller inventory, the
one-commit and the one-release assertions stay.
`.github/scripts/release-pins.test.cjs` gains two cases: a grouped
ci-workflows bump passes with no manifest edit, and two different
ci-workflows releases fail with their locations.
- `docs/releases.md`: states the rule as it now is.

Pins and Dependabot (second commit):

- `.github/workflows/pr-require-checks.yml`: the sixteen ci-workflows
action pins move from v0.73.0 to the v0.74.0
release commit `944d346c487c79eaf85dff752586fb59b0f5c539`. The pin in
the sync-managed
  `pr-check-managed-files-hosted.yml` is unchanged.
- `.github/dependabot.yml`, the `github-actions` entry: the ignore of
`melodic-software/ci-workflows/*` becomes an
ignore of that one sync-managed pin; first-party releases are excluded
from the cooldown; a `first-party-actions`
  group moves every ci-workflows pin in one pull request.

## What the release freshness gate checks for ci-workflows

- Before: the `repositoryPins` commit had to be an ancestor of
ci-workflows' default branch, and drift was counted
from later commits on that branch. No tag or `# v` comment was checked.
- After: as for every other Action, drift is measured against the newest
stable release, exactly one release must
exist for the pinned version, and that release's tag must map to the
pinned commit.
- Lost: the ancestry check and drift counted from unreleased commits.
Gained: the release and tag-to-commit checks.

The published `compatibility.json` never recorded the ci-workflows
commit, so no release artifact changes shape.
No other repository reads `repositoryPins`.

## Verification

- `node --test .github/scripts/workflow-pin-metadata.test.cjs
.github/scripts/release-pins.test.cjs`: 10 pass, 0 fail.
- `pwsh -NoProfile -File scripts/Test-ReleasePins.ps1 -RepositoryRoot
.`: `Release and workflow pins are internally
  consistent.`
- A copy of the tree with all sixteen pins rewritten to another commit
and `# v0.75.0`, manifest untouched: both
  checks pass. With one pin rewritten and fifteen left: both fail.
- standards `components/dependabot-policy/dependabot-policy.mjs --root
.`: `Dependabot policy passed.`
- Not run: `Test-DependencyFreshness.ps1`, which needs the network and
Docker; ci-workflows v0.74.0 is a published
  release whose tag maps to `944d346c`.

## Related

- melodic-software/agent-plugins#143, melodic-software/standards#1026,
#565

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
kyle-sexton added a commit that referenced this pull request Nov 16, 2026
…the cross-cutting record (#147)

Refs: melodic-software/claude-code-plugins#15725

## Summary

Since #137 and #139, #145 moved the check-managed-files pin to
ci-workflows v0.74.0 (`944d346`), and #144 added a header line to
`pr-automerge-dependabot.yml`. The cross-cutting record's notes still
named v0.71.0 and line ranges one line short. This change corrects those
three citations and nothing else.

## Fix

- `check-managed-files@8e1076f v0.71.0` becomes `@944d346 v0.74.0`,
matching `pr-check-managed-files-hosted.yml:118`.
- `pr-automerge-dependabot.yml:21-29` becomes `:22-30` (the job), and
`:3-7` becomes `:3-8` (the header sentence).

No command, version or checksum changes. #143 also moved the
lychee-offline composite to v0.74.0. I diffed it against v0.39.8
(`594987a`): its version (0.24.2), sha256 and argument defaults are
unchanged. It moved its run step into `run.sh` unchanged, and it now
falls back to a bundled `lychee.toml` only when the caller has none;
this repository has one. The other records' citations still hold: apart
from that header line, every CI edit since #139 changed lines in place.

## Verification

- Schema: `check-jsonschema --schemafile
docs/contracts/ecosystem-commands/ecosystem.schema.json`
(claude-code-plugins `origin/main`) over all four records printed `ok --
validation done`.
- Range: from #139's merge `455a89f` to this commit, covering #140
through #146 plus this fix: 8 files (workflows, dependabot, policy.json,
REVIEW.md, the record). Every tool runs with `env -C <checkout>`.
Toolchain skill text is 1.4.0.
- Run 1, `/toolchain:check all`, 11:38 PM to 11:39 PM EST 2026-11-15.
Overall line: `Overall: PASS (1 of 1 ecosystems passed)`.

| Ecosystem | Build | Test | Lint | Status |
|---|---|---|---|---|
| bash | — | — | pass | PASS |
| markdown | — | — | — | — |

- bash: `shellcheck .claude/cloud-bootstrap.sh .cursor/install.sh` and
`bash -n` on each exited 0.
  - markdown: every command is null.
  - No other ecosystem's files exist.
  - The output contains no `skip (unresolved`.
- Run noise: the first attempt ran in a clone nested under another
repository. With no `.shellcheckrc` here, shellcheck took that
repository's rc and reported 9 optional SC2310 infos. The record's
command run from this branch's own checkout exits 0, as on CI's runner.
- Run 2, `/toolchain:lint`, 11:39 PM EST. Overall line: `Overall: PASS
(1 of 1 ecosystems passed)`.
- cross-cutting passed: `jq empty` on both files, lychee with 0 errors,
and `gitleaks dir . --config .gitleaks.toml --no-banner --redact` with
no leaks.
  - markdown and yaml are all null.
  - The installed lychee 0.24.2 and gitleaks 8.30.1 match the pins.
- The verify gate passed on this commit: schema validation plus the
cross-cutting check-cmd.

## Remaining

melodic-software/claude-code-plugins#15725 stays open after this pull
request. Its baseline steps are still owed: a `/toolchain:check all` and
a `/toolchain:lint` with the bundled defaults (records removed) on one
range, then the comparison of their command lists with the record runs
above. This pass had a two-run budget, which went to the record runs.

## Related

- #137 and #139, which merged the records this change corrects
- melodic-software/claude-code-plugins#15725,
melodic-software/claude-code-plugins#15703 (parent)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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