Skip to content

feat(distribution): sync the Dependabot policy to three private repositories - #1036

Merged
kyle-sexton merged 3 commits into
mainfrom
ci/sync-private-repos-dependabot-policy
Nov 16, 2026
Merged

kyle-sexton merged 3 commits into
mainfrom
ci/sync-private-repos-dependabot-policy

Conversation

@kyle-sexton

@kyle-sexton kyle-sexton commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

No related issue: an owner decision in the audit session (2026-11-15), carried out on 2026-11-16.

Summary

architecture, knowledge-corpus and songwriting pin the organization's own ci-workflows actions but have no
synced Dependabot policy copy, so the auto-merge lane cannot arm a first-party bump there and their pins moved
by hand. They become sync targets for the policy copy and, because every sync target must carry one, the
fleet-routed managed-files guard workflow. Nothing else is distributed to them: the hygiene set stays out for the
reasons the manifest's Phase 4 note records.

Fix

  • distribution/sync-manifest.yml: three targets, each managing dependabot-policy and
    managed-files-guard-fleet-caller. Every sync target carries a guard caller; these three run their CI on
    the managed fleet label melodic-ubuntu-24.04-x64, so they take the fleet-routed one. Each therefore gains
    .github/workflows/pr-check-managed-files.yml (PR Check Managed Files), which runs on the fleet, not on a
    hosted runner.
  • components/runner-policy/runner-policy.test.mjs: the three are recorded as private in TARGET_VISIBILITY.
  • distribution/sync-manifest.test.sh: the expected target count goes from 15 to 18.

azure-iac is not added: the sync App must not reach it.

Verification

  • The owner granted the three repositories to the melodic-standards-sync installation (18 selected, "Only
    select repositories") before this merge, the order melodic-software/github-iac's README sets for adding an
    existing repository; the README's selected set is updated in melodic-software/github-iac#901.
  • This pull request's CI Status runs the manifest tests.
  • After the merge, the first unfiltered sync run attests the selected set and opens one pull request in each new
    target; the counts are reported from that run.

Related

🤖 Generated with Claude Code

https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD

…itories

architecture, knowledge-corpus and songwriting pin ci-workflows actions
but hold no policy copy, so the auto-merge lane never arms the
organization's own releases there. Each becomes a target that takes
`dependabot-policy` only (owner decision, 2026-11-15). azure-iac stays
outside the sync.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@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-16T15:26:07.635554Z b04d132 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.

@kyle-sexton kyle-sexton added do-not-merge Hard merge gate: do not merge while applied. and removed do-not-merge Hard merge gate: do not merge while applied. labels Nov 16, 2026
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

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

Incremental security review of distribution/README.md and distribution/sync-manifest.yml (changes since 2a22153). I found no security issues.

Every changed line is a prose edit or a YAML comment. These are the four edits:

  • The README sentence about knowledge-corpus and songwriting now says they are sync targets for dependabot-policy and the fleet-routed guard only.
  • Two comment blocks in sync-manifest.yml were reworded to match.
  • The non-targets comment was reworded to match.
  • The knowledge-corpus and songwriting bullets in the targets: comment were reworded to match.

The diff changes no components: or targets: keys, no locally-owned entries and no workflow, and it touches no trusted-actor list, token scope, kill switch, merge hold or plugin manifest. No code reads these comments, so nothing here changes what gets synced or to whom.

critical-findings: 0

Embedded text: the diff comments cite an "owner decision 2026-11-15" for adding two sync targets. I did not rely on it. Nothing in the diff acts on it, since only comments changed.

Comment thread distribution/sync-manifest.yml Resolved
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

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

Review (incremental, since 2a22153)

The two files changed since the last review are distribution/README.md and distribution/sync-manifest.yml. Both edits are comment and prose rewrites. They now say knowledge-corpus and songwriting take only dependabot-policy and the fleet-routed guard, and they drop the earlier "not sync targets" wording.

I checked those claims against the targets: blocks, and they match. architecture, knowledge-corpus and songwriting each manage exactly dependabot-policy and managed-files-guard-fleet-caller. The surrounding comments (the lychee non-targets note and the Phase 4 non-adoptions) are consistent with that. A repo-wide search found no other "not sync targets" claim about these repos; the remaining hits are about standards itself. The repo's markdownlint config has MD013: false, so the new long lines don't trip a line-length rule. I did not run the test suite.

Findings: 1 (summary only, no changed line can carry it)

  • Stale fleet-routed target list, left over from adding the three targets. The guard sections still name only the six original private targets as receiving the fleet-routed caller. They omit architecture, knowledge-corpus and songwriting, which distribution/sync-manifest.yml now manages with managed-files-guard-fleet-caller. Two places are affected:
    • runs on `ubuntu-24.04` and is `managed` for the public targets. The
      fleet-routed caller runs on `melodic-ubuntu-24.04-x64` and is `managed` for
      the fleet-enrolled private targets (`agent-automations`,
      says the fleet-routed caller is managed for "the fleet-enrolled private targets (agent-automations, claude-code-proxy, dotfiles, github-iac, medley, provisioning)". That is now wrong, and distribution/README.md is a file this PR already edits. The sentence just before it, "No target manages both", is still true.
    • enrolled for local CI routing: `agent-automations`, `claude-code-proxy`,
      `dotfiles`, `github-iac`, `medley`, and `provisioning`. On a routing-enrolled repository,
      has the same six-repo enumeration. It also says the fleet-routed caller is managed for "the private targets enrolled for local CI routing". The three new targets are private but, per the PR description, only run CI on the fleet label; whether they are routing-enrolled in github-iac is not stated.
    • AGENTS.md requires a normative-doc change to reconcile every file that cites or assumes the rule before merge (governance process). Update both lists, or reword them so they don't enumerate the targets.

Manifest items: no plugin manifests changed.

Closing issue: the PR has no closing issue ("No related issue: owner decision").

Embedded instructions: none found in the PR context.

Verification: the PR body's verification claims (the installation grant for the three repos, and the CI Status manifest tests) are author-claimed. I did not confirm them.

Verifier dropped 0 of 1 candidates.

Every sync target carries a managed-files guard caller and a recorded
visibility. The three new private targets run their CI on the managed
fleet label, so they manage the fleet-routed guard and are listed private.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD
@kyle-sexton kyle-sexton added the do-not-merge Hard merge gate: do not merge while applied. label Nov 16, 2026
…id none

Four notes still said knowledge-corpus, songwriting and architecture are
not sync targets. They now say each takes the Dependabot policy copy and
the fleet-routed guard only; the hygiene set stays out for the recorded
reasons (the LFS blocker, github-iac ADR-0006).

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD
@kyle-sexton kyle-sexton removed the do-not-merge Hard merge gate: do not merge while applied. label Nov 16, 2026
@kyle-sexton
kyle-sexton merged commit d726b1c into main Nov 16, 2026
88 of 90 checks passed
@kyle-sexton
kyle-sexton deleted the ci/sync-private-repos-dependabot-policy branch November 16, 2026 15:41
kyle-sexton added a commit that referenced this pull request Nov 16, 2026
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](#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.com/claude-code)

https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD

Co-authored-by: Claude Fable 5.2 <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