Repository navigation
Repair annotated-tag GPU release orchestration safely - #7
Merged
Merged
Conversation
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
1 participant
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.
The v0.1.3 portable gate passed, but GPU source resolution failed before Modal allocation: checkout created a lightweight tag ref and fetching the annotated tag into it was rejected. Fetch into FETCH_HEAD and peel the commit without changing tag refs. A real-Git regression reproduces the failure and verifies the fix.
Add a manual Release repair entry point that builds and publishes an existing immutable tag using updated orchestration. Carry the requested tag through checkout, qualification, version preflight, and publication. Gate direct GPU backfill on a typed input rather than inherited workflow_dispatch, so release repair cannot publish to a nonexistent release. The pypi environment now permits the exact main branch for this validated repair path alongside its existing v* tag rule. Artifact source revisions remain the requested tag; workflow attestations identify the repair workflow separately.
Validation: 55 release tests passed, Ruff, actionlint, git diff --check, and independent review passed. No package source or version changes.