fix(release): Windows verify step runs the raw exe with an explicit relative path - #26
Merged
Conversation
…elative path PowerShell refuses to execute a bare filename from the working directory, so the raw-exe check in the verify job failed on the v0.12.1 run while the zipped exe passed. Test harness only; the published assets verified correctly.
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.
The v0.12.1 verify job failed on Windows only because PowerShell will not run a bare filename from the working directory. The zipped exe (invoked with a path) passed with mark-of-the-web applied, and both checksums matched. Harness fix only. After merge: dispatch the Release workflow with tag v0.12.1 to re-run verify on all three OSes.