Repository navigation
feat(distribution): sync the Dependabot policy to three private repositories - #1036
Conversation
…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>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
claude-security-review reviewed Incremental security review of Every changed line is a prose edit or a YAML comment. These are the four edits:
The diff changes no
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. |
|
claude-review reviewed Review (incremental, since 2a22153)The two files changed since the last review are I checked those claims against the Findings: 1 (summary only, no changed line can carry it)
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 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
…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
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>
No related issue: an owner decision in the audit session (2026-11-15), carried out on 2026-11-16.
Summary
architecture,knowledge-corpusandsongwritingpin the organization's own ci-workflows actions but have nosynced 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 managingdependabot-policyandmanaged-files-guard-fleet-caller. Every sync target carries a guard caller; these three run their CI onthe 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 ahosted runner.
components/runner-policy/runner-policy.test.mjs: the three are recorded as private inTARGET_VISIBILITY.distribution/sync-manifest.test.sh: the expected target count goes from 15 to 18.azure-iacis not added: the sync App must not reach it.Verification
melodic-standards-syncinstallation (18 selected, "Onlyselect 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.
CI Statusruns the manifest tests.target; the counts are reported from that run.
Related
🤖 Generated with Claude Code
https://claude.ai/code/session_01MWmASQ4Dwyfvm2NoX2QpJD