Skip to content

Comments

Fix mixed path separators in NuGet push on Windows#393

Merged
Aaronontheweb merged 1 commit intopetabridge:devfrom
Aaronontheweb:fix/release-nuget-push-paths
Feb 24, 2026
Merged

Fix mixed path separators in NuGet push on Windows#393
Aaronontheweb merged 1 commit intopetabridge:devfrom
Aaronontheweb:fix/release-nuget-push-paths

Conversation

@Aaronontheweb
Copy link
Member

Summary

  • Use PowerShell with $env:GITHUB_WORKSPACE\bin\nuget\*.nupkg (all-backslash Windows paths) for NuGet push — previous ${{ github.workspace }}/bin/nuget/*.nupkg produced mixed separators (D:\a\TurboMqtt\TurboMqtt/bin/nuget/*.nupkg) that dotnet nuget push couldn't resolve
  • Use relative paths for softprops/action-gh-release files — the action uses @actions/glob internally which handles cross-platform paths

Test plan

  • CI passes
  • Release workflow NuGet push step resolves paths correctly after retag

Use PowerShell with $env:GITHUB_WORKSPACE and backslash separators
for dotnet nuget push. Use relative paths for GitHub Release action
which handles glob expansion internally.
@Aaronontheweb Aaronontheweb merged commit 6d5764b into petabridge:dev Feb 24, 2026
3 checks passed
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