Releasing this package should always be a manual process. We might add more automation assistance in the future, but in terms of generating official versions accessible through the public NuGet feed it should always be a human element that initiates this process.
- We're releasing to
production(as in NuGet Gallery) fromtagbuilds - We're releasing canary builds from master to our canary feed
- Verify correct version in Global Properties to
vNext - Verify that the Changelog does not contain any changes from
vCurrent - Check if all changes were listed in the Changelog
- List all closed issues in this release
- List all contributors who helped with this release
- Wait for all changes including documentation to be built
- Automated tests succeed on all supported platforms
- Manual testing on the prerelease build
- Tag the commit we want to release as
vNext - Push
vNexttag as well asmasterbranch changes
vNext-> Name of the version to be releasedvCurrent-> Name of the latest released Version