From 11a8a757e99bb027259857424e0ac0c139e67550 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sun, 15 Nov 2026 13:33:12 -0500 Subject: [PATCH 1/2] ci(dependabot): let Dependabot bump the ci-workflows action pins The four locally owned ci-workflows action pins in pr-require-checks.yml 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 | 25 +++++++++++++++++-------- .github/workflows/pr-require-checks.yml | 8 ++++---- 2 files changed, 21 insertions(+), 12 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 64e2d17..2355997 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -4,10 +4,11 @@ # with a manifest to read here. # # 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. 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. 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 @@ -30,7 +31,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/* @@ -40,8 +50,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 8f9e1f8..7f2b45c 100644 --- a/.github/workflows/pr-require-checks.yml +++ b/.github/workflows/pr-require-checks.yml @@ -253,7 +253,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 @@ -270,7 +270,7 @@ jobs: # `hidden` exists starting at v0.26.0. The v0.24.0 action has no such input, # and without it typos skips `.github/` and `.shellcheckrc`. - name: typos (en-us, hidden files included) - uses: melodic-software/ci-workflows/.github/actions/typos@594987abe8657a40bccc13d301f1f0d5cccb5348 # v0.39.8 + uses: melodic-software/ci-workflows/.github/actions/typos@944d346c487c79eaf85dff752586fb59b0f5c539 # v0.74.0 with: config: _typos.toml hidden: true @@ -301,7 +301,7 @@ jobs: statuses: 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 @@ -309,7 +309,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: results: ${{ join(needs.*.result, ' ') }} # The replaced inline aggregator passed only `success`, so a `skipped` From 16d79799b996a4a385acb2b13939f2e83d67db5b Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sun, 15 Nov 2026 13:33:21 -0500 Subject: [PATCH 2/2] docs(ecosystems): point the lychee and typos record at the pinned commit The cross-cutting record named ci-workflows@594987a (v0.39.8) and line numbers in the lychee-offline and typos actions, and the check-contract and aggregate-results pins, all of which Dependabot now moves at each release. It points at the commits the workflow steps pin and at the actions' input names. The gitleaks citations stay: that composite is not called here. Co-Authored-By: Claude Opus 5.5 --- .claude/ecosystems/cross-cutting.yaml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.claude/ecosystems/cross-cutting.yaml b/.claude/ecosystems/cross-cutting.yaml index 76ed3b2..ef3b2ec 100644 --- a/.claude/ecosystems/cross-cutting.yaml +++ b/.claude/ecosystems/cross-cutting.yaml @@ -5,9 +5,10 @@ # naming check (test-shell job, :119-120), the manifest jq check # (validate-manifests job, :166-169), the relative-link check (check-links job, # :220-239), lychee (lychee job, :255-258) and typos (typos job, :272-276). The -# last two are composites pinned at melodic-software/ci-workflows@594987a -# (v0.39.8). The final line, gitleaks, is the local secret scan, which no CI -# job here runs; notes give its source. Every check runs and any failure fails +# last two are melodic-software/ci-workflows composites at the commits those +# steps pin, which Dependabot moves to each ci-workflows release. The final +# line, gitleaks, is the local secret scan, which no CI job here runs; notes +# give its source. Every check runs and any failure fails # the command. Commands run from the repository root, in bash or zsh. enabled: true globs: ["**"] @@ -54,4 +55,4 @@ tool-pin: typos: "1.50.3" gitleaks: "8.30.1" gates: [] -notes: "Lint-only: owned by /toolchain:lint. Composite lines at ci-workflows@594987a: lychee-offline/action.yml:8, :11, :62 and :74, pins :19 (version) and :24 (checksum); typos/action.yml:9, :12, :98 and :116, pins :46 and :51. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (typos/action.yml:98). CI's typos step also emits annotations from a second json pass (typos/action.yml:105-110); that changes only the output and is left out. CI passes lychee no globs or exclude input (pr-require-checks.yml:257-258), so the defaults '**/*.md' and no --exclude-path apply (lychee-offline/action.yml:8, :16); the glob is single-quoted so lychee expands it, as in CI. Deviations: the relative-link check is CI's script with its comments dropped, its result variable named fail, not status, which zsh holds read-only, and the whole inside a subshell so its exit ends only that check; it uses process substitution, so it needs bash or zsh, not sh. CI checks each manifest with a separate jq call (:166-169); check-cmd keeps that, because one jq call over several files reads them as one stream, so two truncated files could pass together. CI stops each job at its first failing step; check-cmd runs every check. Every check reads the whole tree, not : CI runs each on every change, since no job in this workflow has a path filter (:15-37), and the link checks span files, so a renamed file or heading breaks links in files the change does not touch. A local run reads the working tree, where it can raise findings CI's clean checkout does not: typos walks the tree honoring ignore files (_typos.toml:6), so an untracked file no ignore file covers is spell-checked, for example one under .work/, which .gitignore does not list (.gitignore:1-13); 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 (lychee.toml:11-16, :47-58); the frontmatter glob in markdown.yaml expands on disk. The relative-link check and check-docs-naming.sh list files with git ls-files (pr-require-checks.yml:238; scripts/check-docs-naming.sh:40), so a new file is checked only once it is staged, and a link to an untracked file resolves locally but not in CI. 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 editorconfig-checker or markdownlint command: .editorconfig, .editorconfig-checker.json and .markdownlint-cli2.jsonc are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:7-13; pr-check-managed-files-hosted.yml:41-42, :72), 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. Not run locally: the schema step of the validate-manifests job (pr-require-checks.yml:187-200); typescript.yaml gives the reason. Checks with no local form: the pull-request contract check (pr-require-checks.yml:303-306, check-contract@594987a v0.39.8) and the result aggregation (:307-326, aggregate-results@ac4d878) in the ci-status job (:281-283); 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, :76-78; pr-review-security-hosted.yml:44-46, :69-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:21-29) checks nothing; it arms auto-merge on a Dependabot pull request (:3-7)." +notes: "Lint-only: owned by /toolchain:lint. The lychee and typos commands, versions and checksums are those of ci-workflows' lychee-offline and typos composites at the commits pr-require-checks.yml:256 and :273 pin (lychee-offline's `globs`, `config`, `exclude`, `version` and `sha256` input defaults; typos' `paths`, `config`, `hidden`, `version` and `sha256` input defaults); Dependabot moves those pins to each ci-workflows release, so compare tool-pin with those defaults when a first-party bump merges. CI passes typos hidden: true (pr-require-checks.yml:276), so typos checks dotted paths such as .github/ and .shellcheckrc, with .git/ excluded (the action's `hidden` input). CI's typos step also emits annotations from a second json pass (the action's `annotations` input, default true); that changes only the output and is left out. CI passes lychee no globs or exclude input (pr-require-checks.yml:257-258), 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. Deviations: the relative-link check is CI's script with its comments dropped, its result variable named fail, not status, which zsh holds read-only, and the whole inside a subshell so its exit ends only that check; it uses process substitution, so it needs bash or zsh, not sh. CI checks each manifest with a separate jq call (:166-169); check-cmd keeps that, because one jq call over several files reads them as one stream, so two truncated files could pass together. CI stops each job at its first failing step; check-cmd runs every check. Every check reads the whole tree, not : CI runs each on every change, since no job in this workflow has a path filter (:15-37), and the link checks span files, so a renamed file or heading breaks links in files the change does not touch. A local run reads the working tree, where it can raise findings CI's clean checkout does not: typos walks the tree honoring ignore files (_typos.toml:6), so an untracked file no ignore file covers is spell-checked, for example one under .work/, which .gitignore does not list (.gitignore:1-13); 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 (lychee.toml:11-16, :47-58); the frontmatter glob in markdown.yaml expands on disk. The relative-link check and check-docs-naming.sh list files with git ls-files (pr-require-checks.yml:238; scripts/check-docs-naming.sh:40), so a new file is checked only once it is staged, and a link to an untracked file resolves locally but not in CI. 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 editorconfig-checker or markdownlint command: .editorconfig, .editorconfig-checker.json and .markdownlint-cli2.jsonc are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:7-13; pr-check-managed-files-hosted.yml:41-42, :72), 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. Not run locally: the schema step of the validate-manifests job (pr-require-checks.yml:187-200); typescript.yaml gives the reason. Checks with no local form: the pull-request contract check (pr-require-checks.yml:303-306, check-contract at the commit it pins) and the result aggregation (:307-326, aggregate-results at the same commit) in the ci-status job (:281-283); 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, :76-78; pr-review-security-hosted.yml:44-46, :69-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:21-29) checks nothing; it arms auto-merge on a Dependabot pull request (:3-7)."