Skip to content

feat(distribution): sync the Dependabot policy to .github - #1037

Merged
kyle-sexton merged 1 commit into
mainfrom
feat/sync-dependabot-policy-dot-github
Nov 16, 2026
Merged

kyle-sexton merged 1 commit into
mainfrom
feat/sync-dependabot-policy-dot-github

Conversation

@kyle-sexton

Copy link
Copy Markdown
Member

No related issue: a sync target the first-party action pin work missed.

Summary

melodic-software/.github takes the dependabot-policy sync component, so its auto-merge lane can arm this organization's own releases once its Dependabot stops ignoring melodic-software/ci-workflows.

Fix

distribution/sync-manifest.yml: dependabot-policy added to the .github target's managed list. .github has a pr-automerge-dependabot.yml caller and was the only such target without the policy copy; ci-workflows, the other target without it, has no caller.

Verification

  • bash distribution/sync-manifest.test.sh: exit 0.

Related

  • standards#1036 did the same for three private repositories.
  • The sync opens one pull request in .github (the policy copy and the guard's path list).

🤖 Generated with Claude Code

https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD

The .github repository has a pr-automerge-dependabot caller and no
policy copy, so the auto-merge lane cannot arm this organization's own
releases there. It now takes the dependabot-policy component like the
other targets with that caller.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 16, 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-16T16:57:37.147018Z ebc49e6 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 ebc49e6abb712d2ccf1b0542ed75f551791b5adf: 0 finding(s), 0 as inline comments.

Security review: no findings

The diff is one added line in distribution/sync-manifest.yml. It adds dependabot-policy to the managed list for melodic-software/.github. I read the full diff and the component it names (distribution/sync-manifest.yml:187-189, components/dependabot-policy/policy.json).

  • What it does: it syncs one data-only file, components/dependabot-policy/policy.json, to .github/standards/dependabot-policy/policy.json in that repo. No script, workflow, token request or permission changes. The dependabot-policy component definition is untouched. The same component already syncs to other targets, for example melodic-software/agent-automations.
  • Trust-control widening: none that qualifies. The sync-manifest comment says pr-automerge-dependabot.yml arms the organization's own releases only when the base holds this copy. So the sync lets the fastTrack.own and melodic-software/* tier and the actions/*, github/* and anthropics/* auto tiers apply in .github. That follows the owner decisions recorded in policy.json (2026-11-11, 2026-11-15, 2026-11-16).
    • Who: reaching it needs a malicious release from an owner-controlled repository or an allowlisted publisher. That is not a new trusted actor or a new token scope.
    • What stops it: the policy's own text says CI Status must still pass where an own release lands (policy.json:20).
    • I did not trace the reusable workflow's merge gates beyond this. So the point rests on the policy text and the owner decisions, not on a check of those gates.
  • Hold removals: the diff removes no named friction hold, so I made no throughput-phase exemption.
  • Instruction-surface deletions and plugin manifests: the diff deletes no instruction text and touches no plugin manifest.
  • Protected-class list: I did not consult docs/contracts/instruction-exception-register/README.md. The diff removes no instruction text, so it did not apply.

critical-findings: 0

@github-actions

Copy link
Copy Markdown

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

No findings.

The PR adds dependabot-policy to the melodic-software/.github target's managed list in distribution/sync-manifest.yml. It is a one-line change.

I checked it against the manifest and the component docs:

  • The dependabot-policy component is defined (distribution/sync-manifest.yml:187). Its payload is policy.json alone, delivered to .github/standards/dependabot-policy/policy.json.
  • The component README names the case this PR serves: a target whose pr-automerge-dependabot.yml caller takes its allowlist and fastTrack globs from the policy copy.
  • No manifest comment or README text I read excludes .github from this component. The one remaining check, the manifest test, was not run.
  • The new entry sits in alphabetical order, between commit-convention and editorconfig-checker. Other targets list the component the same way.
  • The PR body follows the contract: No related issue: line, then Summary, Fix, Verification and Related.

I could not run bash distribution/sync-manifest.test.sh myself, because the sandbox required approval for it. The PR body's "exit 0" is the author's claim and I have not confirmed it.

I did not check the claim in the PR body that .github has a pr-automerge-dependabot.yml caller. That file is in another repository.

Verifier dropped 0 of 0 candidates.

@kyle-sexton
kyle-sexton merged commit 683c86f into main Nov 16, 2026
22 checks passed
@kyle-sexton
kyle-sexton deleted the feat/sync-dependabot-policy-dot-github branch November 16, 2026 17:00
kyle-sexton added a commit to melodic-software/.github that referenced this pull request Nov 16, 2026
No related issue: a repository the first-party action pin work missed.

## Summary

The 16 `melodic-software/ci-workflows` composite-action pins in
`pr-require-checks.yml` move to v0.74.0, and Dependabot now bumps them;
the auto-merge lane arms a minor or patch bump of them.

## Fix

- `.github/workflows/pr-require-checks.yml`: 15 pins from v0.39.8 and
one from ac4d878, all to `944d346c487c79eaf85dff752586fb59b0f5c539 #
v0.74.0`. No input this workflow passes was removed and no new input is
required.
- `.github/dependabot.yml`: the `github-actions` entry drops the ignore
of `melodic-software/ci-workflows/*`, ignores `check-managed-files` by
name (the standards sync owns that pin), excludes
`melodic-software/ci-workflows/*` from the cooldown and adds a
`first-party-actions` group.
- `.github/workflows/pr-automerge-dependabot.yml`: header comment only.
- `.claude/ecosystems/*.yaml` and `README.md`: the records cite the
v0.74.0 composite defaults (actionlint is the `kjanat/actionlint` fork
1.17.0, markdownlint-cli2 0.23.3).

Same shape as
[provisioning#1028](melodic-software/provisioning#1028).

## Verification

- `node components/dependabot-policy/dependabot-policy.mjs --root <this
checkout>` from standards main: "Dependabot policy passed.", exit 0.
- `git grep -E '594987a|ac4d878|v0\.39\.8'`: no match.
- The cited action lines were read at the v0.74.0 tag (actionlint
`action.yml:25` and `:67`, markdownlint `:24` and `:57`, gitleaks `:52`,
lychee-offline `:22`, typos `:46`, editorconfig-checker `:35`).
- The lanes themselves run the v0.74.0 actions on this pull request.

## Related

-
[standards#1037](melodic-software/standards#1037)
brought the synced Dependabot policy copy this lane reads.

## Out of scope

- `.cursor/install.sh` pins older tool versions than CI runs, and
`README.md` says they match.

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

https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD

---------

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