ci: Normalize Windows sha256sum output for actions/attest#570
Closed
beekld wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
This isn't right. |
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
Windows release jobs (client, server, server-redis) fail at
actions/attest@v4.1.0withInvalid Argument - subject name length exceeded 256 characters. Git Bash'ssha256sumemits binary-mode output (<hash> *<name>); the attest action only parses text-mode (<hash> <name>), treats the*as a parse fail, and slurps the rest of the file into one giant subject name. Pipe throughsed 's/ \*/ /'to normalize. Linux and macOS produce text-mode output natively.