Chore: Improve logging for NuGet release #159
Merged
Conversation
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
Oleg-Mozhey
changed the title
LukaRukhadze
approved these changes
Mar 10, 2025
Oleg-Mozhey
deleted the
chore/add_better_logging_message_for_nuget_releasing
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds an explicit error message when a 403 response is received, indicating an invalid or expired NuGet API key. This will help users quickly identify issues with the API key and understand how to resolve them. Additionally, a success message is displayed when the package is successfully published to NuGet.org.
Error example if NuGet key is expired:
