[ci] Make sealed scanner rotations transition-safe #14

Closed
opened 2026-08-30 12:42:29 +00:00 by noel · 0 comments
Owner

Deploy source approval deliberately runs the protected-base workflow, so a scanner pin change cannot approve itself after the runner replaces the old binary. codewire/deploy#84 is currently stuck at this boundary.

Keep candidate code non-executing. Seal the current and one explicitly supported compatibility scanner in the hermetic runner, and make the read-only wrapper select only the exact EXPECTED_SUPPLYCHAIN revision already present under /usr/local/libexec. Unknown revisions must fail closed. Add focused contract tests. This is a transition mechanism, not permission to accept arbitrary scanners.

Deploy source approval deliberately runs the protected-base workflow, so a scanner pin change cannot approve itself after the runner replaces the old binary. `codewire/deploy#84` is currently stuck at this boundary. Keep candidate code non-executing. Seal the current and one explicitly supported compatibility scanner in the hermetic runner, and make the read-only wrapper select only the exact `EXPECTED_SUPPLYCHAIN` revision already present under `/usr/local/libexec`. Unknown revisions must fail closed. Add focused contract tests. This is a transition mechanism, not permission to accept arbitrary scanners.
noel closed this issue 2026-08-30 12:50:54 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
noel/act-node-docker#14
No description provided.