Skip to content

ci(dependabot): correct the auto-merge lane comments for first-party actions - #163

Merged
kyle-sexton merged 1 commit into
mainfrom
ci/automerge-first-party-comments
Nov 15, 2026
Merged

kyle-sexton merged 1 commit into
mainfrom
ci/automerge-first-party-comments

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

Two comments described the Dependabot auto-merge lane as it was before the first-party pins moved to Dependabot.
This change corrects them. Comments only: no trigger, permission, group or pin changes.

Fix

  • .github/workflows/pr-automerge-dependabot.yml, header: the lane also arms melodic-software/* bumps, through
    the synced Dependabot policy copy (fastTrack.own), not only the vendor publishers.
  • .github/dependabot.yml: a pull request the lane does not arm takes the review tier (an AI review lane's merge
    verdict), where the comment said a person merges it; and, where the comment covers majors, a first-party major
    stays in first-party-actions instead of falling through to the catch-all group.

Verification

  • ci-workflows pr-automerge-dependabot.yml header on main: with the synced copy at
    .github/standards/dependabot-policy/policy.json, the allowlist is the copy's tier: auto publishers plus its
    fastTrack github-actions and own globs; "a grouped PR with one major bump ... is skipped".
  • standards components/dependabot-policy/policy.json on main: fastTrack.own is melodic-software/*.
  • standards components/dependabot-policy/README.md:183 on main: "No Dependabot pull request waits on a human."
  • git diff touches comment lines only.

Related

🤖 Generated with Claude Code

…actions

The auto-merge caller also arms melodic-software/* bumps when the base
holds the synced Dependabot policy copy, and a first-party major stays in
the first-party-actions group, where the lane does not arm it.

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-15T21:17:40.740832Z 9fda209 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-security-review reviewed 9fda209018e1eb254e862bb1f05753341698538d: 0 finding(s), 0 as inline comments.

No security findings.

The diff is comment-only: it changes .github/dependabot.yml and .github/workflows/pr-automerge-dependabot.yml, and no executable or configuration value moves. I read every changed line.

  • The Dependabot groups, ignore and update-types values are untouched.
  • The workflow's permissions:, triggers, the reusable-workflow uses: pin and the with: inputs are untouched.
  • The comments describe the allowlist and the first-party major-bump behaviour. I checked them against the diff only and did not confirm the allowlist in the reusable workflow, which this PR does not change.
  • No plugin manifest is touched, so no manifest <field> lines apply.
  • No instruction-surface rule is deleted or softened.

critical-findings: 0

@github-actions

Copy link
Copy Markdown

claude-review reviewed 9fda209018e1eb254e862bb1f05753341698538d: 0 finding(s), 0 as inline comments.

No findings. The change is comments only, and I confirmed that against .claude-lane/pr.diff (2 files, no non-comment lines).

  • .github/dependabot.yml comment: it matches the file at head. first-party-actions (melodic-software/*) is declared before vendor-actions (non-major only) and github-actions (*). A first-party major therefore stays in first-party-actions, and a vendor major falls through to github-actions.
  • .github/workflows/pr-automerge-dependabot.yml header: the synced policy copy it cites exists at .github/standards/dependabot-policy. The dependabot.yml cooldown.exclude comment already refers to the same fastTrack.own concept, so the two files agree.
  • Unchanged behavior: no trigger, permission, group, pin or uses: lines changed.
  • Not checked: I did not check the PR's claims about the upstream ci-workflows header and the standards policy.json, so they are author-claimed and unverified. The claim that the reusable skips a grouped PR with one major bump is also author-claimed and unverified.
  • Closing issue: none. The PR uses the "No related issue" escape with a stated reason.
  • Manifests, paved paths, path-scoped rules: no plugin manifest is touched, and nothing in the diff hits them.
  • Embedded instructions: the PR context contains none.

Verifier dropped 0 of 0 candidates.

@kyle-sexton
kyle-sexton merged commit 86f1ceb into main Nov 15, 2026
12 checks passed
@kyle-sexton
kyle-sexton deleted the ci/automerge-first-party-comments branch November 15, 2026 21:18
kyle-sexton added a commit that referenced this pull request Nov 16, 2026
…the cross-cutting record (#166)

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

## Summary

Since #154 and #156, #164 moved the check-managed-files pin to
ci-workflows v0.74.0 (`944d346`), and #163 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. #162 also moved the
lychee-offline and typos composites to v0.74.0. I diffed them against
v0.39.8 (`594987a`): their version, sha256 and argument defaults are
unchanged. lychee-offline 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 #156 changed
lines in place.

## Verification

- Schema: `check-jsonschema --schemafile
docs/contracts/ecosystem-commands/ecosystem.schema.json`
(claude-code-plugins `origin/main`) over all six records printed `ok --
validation done`.
- Method: a throwaway `git clone --shared` of this branch, with
`refs/remotes/origin/main` at #156's merge `c12a04f`. The range runs
#157 through this commit: 16 files, covering workflows, dependabot,
AGENTS.md, REVIEW.md, docs and five SKILL.md. Every tool runs with `env
-C <clone>`. Toolchain skill text is 1.4.0.
- Run 1, `/toolchain:check all`, 11:37 PM to 11:38 PM EST 2026-11-15.
Overall line: `Overall: PASS (3 of 3 ecosystems passed)`.

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

- bash: the sync-local suite has 73 passed, 0 failed and 0 skipped (pwsh
present), and the docs-naming suite has 9 ok. shellcheck and `bash -n`
over CI's list exited 0.
  - powershell: PSScriptAnalyzer reported 0 findings.
  - typescript: every command is null.
  - No dotnet, python or go project files exist.
  - The output contains no `skip (unresolved`.
- Run 2, `/toolchain:lint`, 11:38 PM to 11:39 PM EST. Overall line:
`Overall: PASS (2 of 2 ecosystems passed)`.
  - markdown passed, and yaml is all null.
- cross-cutting passed: check-docs-naming, jq, the relative-link check,
lychee (0 errors), typos, and `gitleaks dir . --config .gitleaks.toml
--no-banner --redact` (no leaks).
  - Installed typos is 1.52.2; the pin is 1.50.3.
- The verify gate passed on this commit: schema validation plus the
cross-cutting check-cmd.

## Remaining

melodic-software/claude-code-plugins#15723 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

- #154 and #156, which merged the records this change corrects
- melodic-software/claude-code-plugins#15723,
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