Repository navigation
Harden exact-SHA GPU qualification and maintainer release gates - #85
Merged
Merged
Conversation
DaoyuanLi2816
marked this pull request as ready for review
August 15, 2026 07:18
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.
Summary
candidate-distributionsplusgpu-full-qualificationfor formal release; retain the complete full evidence set and checksums in workflow and GitHub Release assetsRoot cause and contract
The prior path could forward API credentials across artifact redirects, validated artifact hashes without their declared byte counts, allowed rerun attempts to mix lifecycle boundaries, and accepted diagnostic smoke evidence for formal publication. The release chain is now:
fresh dispatch attempt 1 → hosted candidate bytes → same-run RTX 4080 full qualification → dry-run consumes identical artifacts → tag release publishes identical bytes and full evidenceNo job rebuilds the accepted distributions.
gpu-release-smokeremains useful diagnostics but cannot authorize publication.Validation
9809209479b44d4c413b71d4ad80fb192d86fa2egit diff --checkpassed[train]install completed the real demo8e4b8d6eca11b04326e1d107ce4120a3049ea4c065aab77838c6efb55efa52010e7dc2936b2677e5e4fd856c0682a11419b779cf553be581c585cfb5bcea855e53fc1d4d5b7adee09618d77ad62d4086ba56b78569832d6fc7c3bcd5c2695bbc; no frozen result JSON/JSONL changedExternal boundary
The remote exact-SHA full qualification is intentionally deferred until the final release commit: no self-hosted runner is currently registered. Release and dry-run workflows fail closed until a fresh ephemeral runner produces the required same-run full evidence. This is one measured RTX 4080 stack, not continuous GPU CI; other hardware and distributed verl execution remain unmeasured. No scientific result or capability claim changed, and this PR does not tag or publish a release.