Fix NuGet publish path after .NET 8 upgrade#104
Merged
Conversation
Collaborator
|
Thanks for looking into this failure. I wasn't able to look into it yet. I will merge your changes in and see where things are. There are changes that were rolled back so we need to ensure that all of your changes are still in there |
jryckman
approved these changes
Dec 4, 2025
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.
Justification
The NuGet publishing pipeline failed because the built NuGet package could not be located. This issue occurred after upgrading to .NET 8 (see #102), as the build configuration is now included in the NuGet path.
Implementation
Update the path to the nupkg to include
ReleaseTesting
Verified the new path exists.