DashboardpublishEnforce defense-in-depth in release wor…

Enforce defense-in-depth in release workflows

Category: preference
Confidence: 0.80
ID: 01a089dd-012e-70ef-aa94-a26cf95fdd97
Project ID: ac098440-8723-4582-9021-39e07a608100
Cross-project: No
Recalled in other projects: 0
Source session: 1MdXRLzzwzI66jNKD
Created: 2026-09-10 05:49:17
Updated: 2026-09-10 05:49:17

Content

When modifying GitHub Actions release, approval, or CI-poller flows, preserve strict trust boundaries and fail closed. Run only trusted default-branch code before accessing tokens, keep secret-bearing jobs behind the protected production environment, prevent dispatched refs from receiving secrets, and pin actions and containers to immutable digests. Bind approvals to immutable request details and current label-event IDs, prohibit self-approval, and revalidate attestations immediately before every privileged state transition or publish operation. If the request or approval changes, remove approval-related labels and stop rather than continuing. Add focused automated tests that enforce workflow ordering, token identity, action pinning, dispatch restrictions, exact body preservation, cleanup, and race-condition handling.

Move to: