From c923ec9714dd8b50bc3cbeff31bf740ab3092d65 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sun, 15 Nov 2026 13:33:22 -0500 Subject: [PATCH 1/2] ci(dependabot): let Dependabot bump the ci-workflows action pins 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 --- .github/dependabot.yml | 27 ++++++++++++++++--------- .github/workflows/pr-require-checks.yml | 6 +++--- 2 files changed, 21 insertions(+), 12 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index aade481..f4c8c86 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -4,11 +4,12 @@ # tooling has no lockfile and no runtime dependencies to track. # # Merge lanes follow the standards dependabot-policy component: the -# `vendor-actions` group (non-major only) is the auto-merge lane armed by -# pr-automerge-dependabot.yml; every other PR is reviewed by hand and runs -# `pr-require-checks` before a human merges it. A dependency joins the first -# group that matches it, so majors fall through to the reviewed `github-actions` -# group. +# `first-party-actions` group (the melodic-software/ci-workflows composite +# action pins) and the `vendor-actions` group (non-major only) are the +# auto-merge lanes armed by pr-automerge-dependabot.yml; every other PR is +# reviewed by hand and runs `pr-require-checks` before a human merges it. A +# dependency joins the first group that matches it, so majors fall through to +# the reviewed `github-actions` group. version: 2 updates: - package-ecosystem: github-actions @@ -27,7 +28,16 @@ updates: # security-advisory updates bypass cooldown and still surface immediately. cooldown: default-days: 3 + # First-party releases take no soak (the synced Dependabot policy's + # `fastTrack.own`). + exclude: + - "melodic-software/ci-workflows/*" groups: + # Every ci-workflows composite-action pin moves in one pull request, so + # the repository stays on one ci-workflows release. + first-party-actions: + patterns: + - "melodic-software/*" vendor-actions: patterns: - actions/* @@ -37,8 +47,7 @@ updates: github-actions: patterns: - "*" - # Every melodic-software/ci-workflows ref (reusable workflows AND composite - # actions) moves only through deliberate reviewed PRs per the standards - # runner-policy selector-revision lockstep, so all of them are ignored here. + # The one first-party pin Dependabot leaves alone sits in the sync-managed + # pr-check-managed-files-hosted.yml, which the standards sync owns. ignore: - - dependency-name: "melodic-software/ci-workflows/*" + - dependency-name: "melodic-software/ci-workflows/.github/actions/check-managed-files" diff --git a/.github/workflows/pr-require-checks.yml b/.github/workflows/pr-require-checks.yml index afe8c99..9a543a8 100644 --- a/.github/workflows/pr-require-checks.yml +++ b/.github/workflows/pr-require-checks.yml @@ -101,7 +101,7 @@ jobs: with: persist-credentials: false - name: Check local links and anchors - uses: melodic-software/ci-workflows/.github/actions/lychee-offline@594987abe8657a40bccc13d301f1f0d5cccb5348 # v0.39.8 + uses: melodic-software/ci-workflows/.github/actions/lychee-offline@944d346c487c79eaf85dff752586fb59b0f5c539 # v0.74.0 with: config: lychee.toml @@ -128,7 +128,7 @@ jobs: actions: write steps: - name: Check the pull-request contract - uses: melodic-software/ci-workflows/.github/actions/pr-require-checks/check-contract@594987abe8657a40bccc13d301f1f0d5cccb5348 # v0.39.8 + uses: melodic-software/ci-workflows/.github/actions/pr-require-checks/check-contract@944d346c487c79eaf85dff752586fb59b0f5c539 # v0.74.0 with: token: ${{ github.token }} - name: Aggregate lane results @@ -136,7 +136,7 @@ jobs: # aggregation: the job still fails on the contract step's exit code, and # the `ci-lanes` status is on the SHA for the next contract-only run. if: ${{ !cancelled() }} - uses: melodic-software/ci-workflows/.github/actions/pr-require-checks/aggregate-results@ac4d8780de793b20e60a66890e767df579c80d83 # ac4d878 2026-11-11 + uses: melodic-software/ci-workflows/.github/actions/pr-require-checks/aggregate-results@944d346c487c79eaf85dff752586fb59b0f5c539 # v0.74.0 with: # A contract-only run never waits: while a full run on the SHA is in # flight it fails with "superseded by full run ", and that run's From 2809a112e931913020591a3e498182ae281d4966 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sun, 15 Nov 2026 13:33:30 -0500 Subject: [PATCH 2/2] docs(ecosystems): point the lychee record at the pinned commit 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 --- .claude/ecosystems/cross-cutting.yaml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml index 7a9da86..9f36182 100644 --- a/.claude/ecosystems/cross-cutting.yaml +++ b/.claude/ecosystems/cross-cutting.yaml @@ -2,12 +2,13 @@ # https://github.com/melodic-software/claude-code-plugins/tree/main/docs/contracts/ecosystem-commands # Lint-only: /toolchain:lint runs it, /toolchain:check does not. Two checks. # lychee is CI's lychee job (.github/workflows/pr-require-checks.yml:93-106), -# the lychee-offline composite pinned at melodic-software/ci-workflows@594987a -# (v0.39.8) with this repository's lychee.toml (:104-106); the command is the -# composite's arguments (lychee-offline/action.yml:62) with its default glob -# (:8), which it passes to lychee unexpanded (:72-74). gitleaks is the local -# secret scan, which no CI job here runs; notes give its source. Both run and -# any failure fails the command. Commands run from the repository root. +# the melodic-software/ci-workflows lychee-offline composite at the commit +# that step pins, which Dependabot moves to each ci-workflows release, with this +# repository's lychee.toml (:104-106); the command is the composite's arguments +# with its `globs` input default, which it passes to lychee unexpanded. gitleaks +# is the local secret scan, which no CI job here runs; notes give its source. +# Both run and any failure fails the command. Commands run from the repository +# root. enabled: true globs: ["**"] project-discovery: [] @@ -28,4 +29,4 @@ tool-pin: lychee: "0.24.2" gitleaks: "8.30.1" gates: [] -notes: "Lint-only: owned by /toolchain:lint. Pins at ci-workflows@594987a: lychee-offline/action.yml:19 (version), :24 (checksum), :40 (asset). CI passes no globs or exclude input (pr-require-checks.yml:105-106), so the defaults '**/*.md' and no --exclude-path apply (action.yml:8, :16). The glob is single-quoted so lychee expands it, as in CI; an unquoted ** in a shell without globstar matches one directory level only. check-cmd checks every markdown file, not : an anchor check spans files, so a changed heading breaks links in files the change does not touch. A local run reads the working tree: lychee.toml sets hidden = true and a glob input does not honor .gitignore, so ignored dot-directories other than the excluded .work/ and .claude/worktrees/ are read too (lychee.toml:11-16, :47-58), which CI's clean checkout does not have. Deviation from CI: gitleaks. No CI job in this repository runs gitleaks; the line keeps the local secret scan that the bundled cross-cutting default ran before this file existed (claude-code-plugins plugins/toolchain/reference/ecosystems/cross-cutting.yaml:12, opt-in :18, met by the tracked .gitleaks.toml), so these records do not switch a secret scan off. Its command, version and checksum are those of the gitleaks composite at ci-workflows@594987a (v0.39.8), which this repository does not call: gitleaks/scan.sh:113, :136 and :142 with the defaults at gitleaks/action.yml:9, :15 and :30, pins :50 (version) and :55 (checksum). gitleaks scans every file on disk under the repository root, tracked, untracked or git-ignored (a scratch file under .work/ included), and not git history; it does not read . No typos or editorconfig-checker command: _typos.toml, .editorconfig and .editorconfig-checker.json are standards-synced files (pr-check-managed-files-hosted.yml:41-42, :76), and no CI job here runs those tools; lefthook.yml:1-6 pulls git hooks from claude-code-plugins, and apart from gitleaks these records follow CI, not a local hook. Checks with no local form: the pull-request contract check (pr-require-checks.yml:130-133, check-contract@594987a v0.39.8) and the result aggregation (:134-153, aggregate-results@ac4d878) in the ci-status job (:108); they need the pull request. This ci-status job has no draft refusal. Not run locally: the model review lanes pr-review (.github/workflows/pr-review-hosted.yml:74-85) and pr-review-security (.github/workflows/pr-review-security-hosted.yml:67-78), which review the pull request through ci-workflows reusables called at @main, not pinned; both are advisory and skip drafts (pr-review-hosted.yml:37-38, :78; pr-review-security-hosted.yml:44-46, :71). Not run locally: check-managed-files (pr-check-managed-files-hosted.yml:106-127, check-managed-files@8e1076f v0.71.0), which needs a melodic-software/standards checkout and the pull request; it is advisory and not aggregated into ci-status (:20-22). pr-automerge-dependabot (.github/workflows/pr-automerge-dependabot.yml:22-29) checks nothing; it arms auto-merge on a Dependabot pull request (:3-7)." +notes: "Lint-only: owned by /toolchain:lint. The lychee version, checksum and release asset are those of ci-workflows' lychee-offline/action.yml at the commit pr-require-checks.yml:104 pins (its `version` and `sha256` input defaults and its install step's asset URL); Dependabot moves that pin to each ci-workflows release, so compare tool-pin and install-hint with those defaults when a first-party bump merges. CI passes no globs or exclude input (pr-require-checks.yml:105-106), so the defaults '**/*.md' and no --exclude-path apply (the action's `globs` and `exclude` defaults). The glob is single-quoted so lychee expands it, as in CI; an unquoted ** in a shell without globstar matches one directory level only. check-cmd checks every markdown file, not : an anchor check spans files, so a changed heading breaks links in files the change does not touch. A local run reads the working tree: lychee.toml sets hidden = true and a glob input does not honor .gitignore, so ignored dot-directories other than the excluded .work/ and .claude/worktrees/ are read too (lychee.toml:11-16, :47-58), which CI's clean checkout does not have. Deviation from CI: gitleaks. No CI job in this repository runs gitleaks; the line keeps the local secret scan that the bundled cross-cutting default ran before this file existed (claude-code-plugins plugins/toolchain/reference/ecosystems/cross-cutting.yaml:12, opt-in :18, met by the tracked .gitleaks.toml), so these records do not switch a secret scan off. Its command, version and checksum are those of the gitleaks composite at ci-workflows@594987a (v0.39.8), which this repository does not call: gitleaks/scan.sh:113, :136 and :142 with the defaults at gitleaks/action.yml:9, :15 and :30, pins :50 (version) and :55 (checksum). gitleaks scans every file on disk under the repository root, tracked, untracked or git-ignored (a scratch file under .work/ included), and not git history; it does not read . No typos or editorconfig-checker command: _typos.toml, .editorconfig and .editorconfig-checker.json are standards-synced files (pr-check-managed-files-hosted.yml:41-42, :76), and no CI job here runs those tools; lefthook.yml:1-6 pulls git hooks from claude-code-plugins, and apart from gitleaks these records follow CI, not a local hook. Checks with no local form: the pull-request contract check (pr-require-checks.yml:130-133, check-contract at the commit it pins) and the result aggregation (:134-153, aggregate-results at the same commit) in the ci-status job (:108); they need the pull request. This ci-status job has no draft refusal. Not run locally: the model review lanes pr-review (.github/workflows/pr-review-hosted.yml:74-85) and pr-review-security (.github/workflows/pr-review-security-hosted.yml:67-78), which review the pull request through ci-workflows reusables called at @main, not pinned; both are advisory and skip drafts (pr-review-hosted.yml:37-38, :78; pr-review-security-hosted.yml:44-46, :71). Not run locally: check-managed-files (pr-check-managed-files-hosted.yml:106-127, check-managed-files@8e1076f v0.71.0), which needs a melodic-software/standards checkout and the pull request; it is advisory and not aggregated into ci-status (:20-22). pr-automerge-dependabot (.github/workflows/pr-automerge-dependabot.yml:22-29) checks nothing; it arms auto-merge on a Dependabot pull request (:3-7)."