Skip to content

Fix importer NuGet push step (glob not expanded)#57

Merged
StuartMeeks merged 1 commit into
mainfrom
fix/importer-nuget-push-glob
Jun 8, 2026
Merged

Fix importer NuGet push step (glob not expanded)#57
StuartMeeks merged 1 commit into
mainfrom
fix/importer-nuget-push-glob

Conversation

@StuartMeeks

Copy link
Copy Markdown
Owner

The v1.0.2 release published the app fine but the NuGet push step failed:

```
error: File does not exist (nuget/*.nupkg).
```

The step ran `dotnet nuget push "nuget/*.nupkg"` under PowerShell, which doesn't expand wildcards for native commands, and `dotnet nuget push` takes the pattern literally — so the package (correctly produced in `nuget/`) was never found.

Fix

Resolve the `.nupkg` explicitly with `Get-ChildItem` and push its full path.

Note

The 1.0.2 importer package was published manually as a one-off (clean `1.0.2`), so this fix is what makes future tagged releases push the importer automatically. No version bump here — it's a CI-only fix.

🤖 Generated with Claude Code

The push step relied on shell glob expansion of nuget/*.nupkg, but the step runs
under PowerShell, which does not expand wildcards for native commands, and
'dotnet nuget push' takes the pattern literally — so it failed with
'File does not exist (nuget/*.nupkg)' while the package sat in nuget/.

Resolve the package with Get-ChildItem and push its full path instead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@StuartMeeks StuartMeeks merged commit daa9f09 into main Jun 8, 2026
6 checks passed
@StuartMeeks StuartMeeks deleted the fix/importer-nuget-push-glob branch June 8, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant