Skip to content

images: a release spin-stack/ami marked revoked is not installed - #27

Merged
aledbf merged 1 commit into
mainfrom
images/revoked
Oct 4, 2026
Merged

aledbf merged 1 commit into
mainfrom
images/revoked

Conversation

@aledbf

@aledbf aledbf commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

F9 of the sealed-workspaces plan, the registry's part (spin-stack/ami#47 is the image's, spin#284 spin's; the three merge together).

spin-stack/ami's task images:revoke RELEASE= ROLE= REASON= opens a pull request here marking that build revoked in measurements.json (revoked: why, revoked_at: the day). The entry keeps its PCRs and statement, so what was published stays checkable.

This PR makes the control plane's module refuse to plan a release with a revoked image. It names which image and why, before anything of it is made, so an installation on it is told on its next plan to move spin_version. image_measurements, which mirrors an entry, carries revoked too.

Test: a_revoked_release_is_not_installed (planted: a precondition that never fails is caught). task lint: 45/45 module tests.

🤖 Generated with Claude Code

F9 of the sealed-workspaces plan: spin-stack/ami's `task images:revoke` marks
a build revoked in measurements.json, with why (`revoked`, `revoked_at`). The
control plane's module now refuses to plan a release with a revoked image,
naming which and why, before anything of it is made: an installation on it is
told on its next plan to move spin_version. image_measurements, which mirrors
an entry, carries `revoked` too.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@aledbf
aledbf merged commit afbb639 into main Oct 4, 2026
2 checks passed
@aledbf
aledbf deleted the images/revoked branch October 4, 2026 04:37
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