-
Notifications
You must be signed in to change notification settings - Fork 9
Fix Windows release attestation and artifact verifier #586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
AnthonyRonning
merged 1 commit into
master
from
fix/windows-artifact-attestation-verifier
Jun 26, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚩 Runtime manifest verification no longer checks actual file hashes
The old code called
verify_file_manifeston the runtime DLLs manifest (verify-release-artifacts.sh:432), which attempts to locate each referenced artifact file and verify its SHA256 hash. The newverify_windows_runtime_manifestfunction (verify-release-artifacts.sh:128-195) only validates the manifest structure — correct hash format, expected DLL names, no duplicates, all expected DLLs present — but never verifies the hash values against actual files. This is likely intentional because the DLL files (MSVCP140.dll, VCRUNTIME140.dll, etc.) are not uploaded as artifacts; only the manifest.sha256proof file is uploaded. The oldverify_file_manifestwould have failed whenartifact_for_labelatverify-release-artifacts.sh:115tried to find these DLLs in the downloaded artifacts directory. This raises the question of whether the old path was ever exercised successfully in production, or whether the runtime manifest was always absent/empty in practice prior to this change.Was this helpful? React with 👍 or 👎 to provide feedback.