[repo] Release process tweaks & improvements #5584
Merged
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.
Changes
Details
We have a quirk in the release process today where we create the GitHub release to trigger the build. The actual packages don't get pushed to NuGet until much later. This creates confusion for users who see the release but don't find the packages. In order to smooth this out, we now trigger the build+pack workflow on the tag push. The GitHub release is now also automatically created as a draft so whoever is doing a release need only publish that release when the packages are available. The content of the release is automatically generated with links to NuGet & the CHANGELOGs which is what we do on contrib. The net is there is less manual work in the release process.
Merge requirement checklist