Verify Windows CLI releases - #12
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
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.
What changed
version, andalertssmoke checks onwindows-latestchecksums.txt, extracts it, and runs the released executableWhy
The WinGet 0.1.3 installation validator returned a generic failure even though its progress report showed both x64 and ARM64 reaching
Completedwith the expected URLs and hashes. The existing Linux checks cannot prove that the Windows binary itself starts and handles its core commands.This gives each future release a direct Windows check and gives us a repeatable way to verify an already published archive before asking a package moderator to rerun external validation.
Validation
go test -race ./...go vet ./...actionlintgit diff --check