Fix Windows build by using GitHub Actions expressions directly & release 0.1.1 - #6
Merged
Conversation
PowerShell doesn't expand $VARIABLE the same way bash does. Using
${{ matrix.targets.target }} directly in the run commands fixes this.
lfrancke
force-pushed
the
release-0.1.1
branch
from
October 13, 2025 11:05
577002f to
b534663
Compare
PowerShell doesn't expand $VARIABLE the same way bash does. Using
${{ matrix.targets.target }} directly in the run commands fixes this.
lfrancke
force-pushed
the
release-0.1.1
branch
from
October 13, 2025 11:07
b534663 to
c91816c
Compare
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
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.
PowerShell doesn't expand
$VARIABLEthe same way bash does. Using${{ matrix.targets.target }}directly in the run commands hopefully fixes this.