fix: hardcode Microsoft SBOM tool checksum#22
Merged
ramonclaudio merged 1 commit intomainfrom Sep 7, 2025
Merged
Conversation
- Microsoft doesn't provide .sha256 files for their releases - Use hardcoded SHA256 checksum for v4.1.2 - Remove reference to non-existent .sha256 file in cleanup
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.
Summary
Problem
The workflow was failing with:
Microsoft doesn't provide .sha256 files for their SBOM tool releases.
Solution
Use a hardcoded checksum like we did for minisign:
Testing
This ensures the Microsoft SBOM tool is properly verified and the workflow completes successfully.