fix: Use bash to expand glob in NuGet push step - #995
Merged
Conversation
PowerShell doesn't glob-expand arguments to external commands, so `bin/*.nupkg` was passed to dotnet nuget push literally on windows-latest, which failed to resolve the wildcard itself and errored with "File does not exist (bin/*.nupkg)" even though the package existed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
2 participants
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.
Follow up on #987.
I didn't have a chance to test it and apparently there are issues with globbing and powershell. Let's try this change and see if it helps. You'll have to re-create the tag. Just delete the tag and then go to releases and create it one more time :)