You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Run NuGet release publishing from the package output directory - #719
The v1.9.0 release run built both packages and authenticated to NuGet.org successfully, then failed with File does not exist (out/*.nupkg).
Set the publish step's working-directory to out and run dotnet nuget push "*.nupkg", avoiding a directory separator in the package pattern. The final workflow change is one added setting and one changed command.
Validation: actionlint v1.7.12 and git diff --check passed. Tested the same wildcard command from the output directory against a temporary local NuGet feed; both smoke packages were pushed successfully. No external packages were published during validation.
The existing v1.9.0 run retains its original tagged workflow when rerun. Its built packages remain available for manual recovery.
Summary by CodeRabbit
Chores
Updated the release process to publish generated NuGet packages from the correct output location.
Shane32/QRCoder#718: This PR changes the same release workflow and adds NuGet authentication used by the publish step.
Merge Risk: Minimal · up to ffcc9
The release workflow now publishes the built packages from the output directory, which fixes the earlier missing-file failure. No remaining merge-blocking risk was found.
Pre-merge checks: 2
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title accurately describes the main change: the NuGet release publish step now runs from the out directory so the *.nupkg pattern resolves correctly. The raw summary confirms that the workflow pub…
Full details: Title check
Explanation
The title accurately describes the main change: the NuGet release publish step now runs from the out directory so the *.nupkg pattern resolves correctly. The raw summary confirms that the workflow publish step runs from out and pushes *.nupkg there. The objectives describe the same fix, which sets working-directory to out and changes the push pattern to *.nupkg, matching the title.
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: dc275983-72a0-4030-8423-478a83190a49
Commits
Reviewing files that changed from the base of the PR and between 2f4504a and 8ddf811.
Files selected for processing: 1
.github/workflows/wf-build-release.yml
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 6 remain after this review.
Shane32
changed the title
Fix package discovery when publishing NuGet releases on Windows
Run NuGet release publishing from the package output directory
Nov 19, 2026
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
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 v1.9.0 release run built both packages and authenticated to NuGet.org successfully, then failed with
File does not exist (out/*.nupkg).Set the publish step's
working-directorytooutand rundotnet nuget push "*.nupkg", avoiding a directory separator in the package pattern. The final workflow change is one added setting and one changed command.Validation:
actionlintv1.7.12 andgit diff --checkpassed. Tested the same wildcard command from the output directory against a temporary local NuGet feed; both smoke packages were pushed successfully. No external packages were published during validation.The existing v1.9.0 run retains its original tagged workflow when rerun. Its built packages remain available for manual recovery.
Summary by CodeRabbit