ci: recover attested partial releases - #26
Merged
Merged
Conversation
Reuse verified artifacts from a tag-triggered release run after recovery tooling changes, while preserving the original tag commit and registry provenance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an idempotent recovery mode to the existing trusted release workflow for the case where a registry accepts an artifact and later verification tooling needs a source fix.
A manual
publish.ymldispatch names the protected release tag and the failed release run. The recovery preflight requires currentmain, an annotated tag whose commit remains on main, a tag-triggered Release run for that exact commit, and successful build and provenance jobs. The workflow downloads that run's immutable artifacts, verifies their package contracts, republishes matching npm artifacts idempotently, and continues npm verification, PyPI trusted publishing, public Python verification, and GitHub Release creation.Normal tag releases keep the existing full build path. Recovery reuses the same downstream environments and least-privilege OIDC jobs, so registry authority remains scoped to
npmandpypi.