fix(sync): keep legacy orchestrator protected - #2162
Conversation
There was a problem hiding this comment.
Pull request overview
This PR tightens the agents-guard removal allowlist so the legacy unnumbered orchestrator workflow (.github/workflows/agents-orchestrator.yml) remains protected (removal is blocked), while still allowlisting cleanup of the numbered legacy orchestrator (agents-70-orchestrator.yml) for template-sync bootstrap scenarios. It also adds regression coverage in both the Node and Python test suites to prevent this policy from drifting again.
Changes:
- Remove
.github/workflows/agents-orchestrator.ymlfrom the consumer-only removal allowlist in agents-guard. - Keep
.github/workflows/agents-70-orchestrator.ymlallowlisted for consumer repos (but still blocked instranske/Workflows). - Add JS + Python regression tests asserting unnumbered orchestrator deletions are blocked and the numbered orchestrator remains allowlisted for consumer repos.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
tests/workflows/test_agents_guard.py |
Updates deletion-blocking fixtures to a non-allowlisted workflow and adds a Python regression test that deletion of agents-orchestrator.yml is blocked in consumer repos. |
templates/consumer-repo/.github/scripts/agents-guard.js |
Removes agents-orchestrator.yml from the consumer-only removal allowlist (template copy). |
.github/scripts/agents-guard.js |
Removes agents-orchestrator.yml from the consumer-only removal allowlist (source-of-truth copy). |
.github/scripts/__tests__/agents-guard.test.js |
Adjusts allowlist coverage and adds a JS regression test that agents-orchestrator.yml removals are blocked in consumer repos. |
Automated Status SummaryHead SHA: acafe86
Coverage Overview
Coverage Trend
Top Coverage Hotspots (lowest coverage)
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
Related to campaign issue #1836
Automated Status Summary
Scope
Sync/Dependabot Campaign Queue
Durable tracker — see
docs/ops/DURABLE_TRACKING_ISSUES.md. The body below is regenerated each cycle bymaint-82-sync-dependabot-campaign.yml; do not close as part of routine triage.Remote discovery found more review-thread work than fits in a full GitHub issue body. The marker below retains the compact machine-readable queue for the local watcher.
Context for Agent
Related Issues/PRs
Tasks
Acceptance criteria
Head SHA: 56669d6
Latest Runs: ✅ success — Gate
Required: gate: ✅ success