Repository navigation
Fix v0.11 release evidence environment binding - #103
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
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
Reproduction
The exact qualification from run 33285177196 fails validation with the legacy manifest checksum and passes with the WSL2 manifest checksum. The release dry run therefore reached every preceding gate successfully but failed
release_evidence_chainbefore this fix.Validation
pytest -q tests/unit/test_release_gate.py tests/unit/test_release_workflow.py(18 passed)ruff check scripts/release_gate.py tests/unit/test_release_gate.pyruff format --check scripts/release_gate.py tests/unit/test_release_gate.pygit diff --checkAfter merge, the candidate and full GPU qualification will be rerun against the new source SHA before release.