Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions .claude/ecosystems/cross-cutting.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,9 @@
# Lint-only: /toolchain:lint runs it, /toolchain:check does not. Each line is a
# step of .github/workflows/pr-require-checks.yml, in its job order: the
# manifest jq check (check-scripts-and-manifests job, :103-106) and lychee
# (lychee job, :118-121), a composite pinned at
# melodic-software/ci-workflows@594987a (v0.39.8). The final line, gitleaks, is
# (lychee job, :118-121), the melodic-software/ci-workflows lychee-offline
# composite at the commit that step pins, 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.
Expand All @@ -31,4 +32,4 @@ tool-pin:
lychee: "0.24.2"
gitleaks: "8.30.1"
gates: []
notes: "Lint-only: owned by /toolchain:lint. Composite lines at ci-workflows@594987a: lychee-offline/action.yml:8, :11, :16, :62 and :74, pins :19 (version) and :24 (checksum), asset :40. The lychee step passes only the input config: lychee.toml (pr-require-checks.yml:118-121), 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. jq has no tool-pin: CI uses the runner image's jq (pr-require-checks.yml:94-95). Deviations: CI's jq step runs two jq calls in a run step with no shell key, under bash -e, so it stops at the first failure (:103-106), and the job stops at its first failing step; check-cmd keeps the two separate calls, because one jq call over several files reads them as one stream, so two truncated files could pass together, and runs every check, failing when any fails. No check reads <files>: jq reads its two named manifests and lychee all markdown, as CI does on every change, since no job in this workflow has a path filter (:12-37). The jq file list copies CI's (:105-106); when CI's list changes, change it here. Links 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 lychee can raise findings CI's clean checkout does not: lychee.toml sets hidden = true and a glob input does not honor .gitignore (lychee.toml:11-16), so an untracked *.md is checked unless it sits under a path lychee.toml excludes (:47-58), for example .work/ or .claude/worktrees/. 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 would run without this file (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 <files>. No typos or editorconfig-checker command: without this file the bundled default (cross-cutting.yaml:11, :14) would run both, because their configs, _typos.toml and .editorconfig-checker.json, meet its opt-in (:18); those are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:6-10; .github/workflows/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; 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:145-150, check-contract@594987a v0.39.8) and the result aggregation (:151-170, aggregate-results@ac4d878) in the ci-status job (:123-170); 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, :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 command, version and checksum are those of ci-workflows' lychee-offline/action.yml at the commit pr-require-checks.yml:119 pins (its `globs`, `config`, `exclude`, `version` and `sha256` input defaults); Dependabot moves that pin to each ci-workflows release, so compare tool-pin with those defaults when a first-party bump merges. The lychee step passes only the input config: lychee.toml (pr-require-checks.yml:118-121), 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. jq has no tool-pin: CI uses the runner image's jq (pr-require-checks.yml:94-95). Deviations: CI's jq step runs two jq calls in a run step with no shell key, under bash -e, so it stops at the first failure (:103-106), and the job stops at its first failing step; check-cmd keeps the two separate calls, because one jq call over several files reads them as one stream, so two truncated files could pass together, and runs every check, failing when any fails. No check reads <files>: jq reads its two named manifests and lychee all markdown, as CI does on every change, since no job in this workflow has a path filter (:12-37). The jq file list copies CI's (:105-106); when CI's list changes, change it here. Links 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 lychee can raise findings CI's clean checkout does not: lychee.toml sets hidden = true and a glob input does not honor .gitignore (lychee.toml:11-16), so an untracked *.md is checked unless it sits under a path lychee.toml excludes (:47-58), for example .work/ or .claude/worktrees/. 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 would run without this file (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 <files>. No typos or editorconfig-checker command: without this file the bundled default (cross-cutting.yaml:11, :14) would run both, because their configs, _typos.toml and .editorconfig-checker.json, meet its opt-in (:18); those are standards-synced files that CI deliberately does not re-lint (pr-require-checks.yml:6-10; .github/workflows/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; 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:145-150, check-contract at the commit it pins) and the result aggregation (:151-170, aggregate-results at the same commit) in the ci-status job (:123-170); 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, :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)."
25 changes: 17 additions & 8 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,11 @@ version: 2
# here, so no glob target is needed; add one if composite actions land.
#
# 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.
updates:
- package-ecosystem: github-actions
directory: /
Expand All @@ -27,7 +28,16 @@ updates:
# this repository adopts it; security updates bypass the cooldown.
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/*
Expand All @@ -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"
6 changes: 3 additions & 3 deletions .github/workflows/pr-require-checks.yml
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,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

Expand Down Expand Up @@ -145,15 +145,15 @@ jobs:
- name: Check the pull-request contract
# A `push` or `merge_group` run carries no pull-request number, which
# makes this step a no-op reporting every output as `skipped`.
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
# `!cancelled()` so a failing check-contract step does not skip the
# 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 <url>", and that run's
Expand Down
Loading