NuGet: Add release notes to packages #154
Closed
Conversation
This file contains 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
|
I don't think we'll manage to pass a multiline string to the command line. |
|
On nuget.org, I could find very few packages that define the release notes, and the ones I found only included a link to an external page. |
Then how about doing just that. :-) This one has no fallback if the chromium branch was unset. Maybe something like |
|
|
|
@jerbob92 Lookin' great! 😊 |
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.
The GitHub releases have these nice auto-generated release notes containing the chromium branch name and commit messages. It would be great to have these for the NuGet packages, too.
NuGet release notes are plain text and don't support markdown (NuGet/NuGetGallery#8889) so the format and URLs had to be stripped.
I haven't tested this change myself so it would be a good idea to double check if this bash script/workflow yaml looks correct.