Skip to content

DEPLOYMENT.md

Latest commit

 

History

History
19 lines (16 loc) · 1.21 KB

DEPLOYMENT.md

File metadata and controls

19 lines (16 loc) · 1.21 KB

Deploying a new release

Deployment is hard. There are too many manual steps. Let's at least enumerate them so everyone is on the same page.

Assuming all changes for the new release are commited, tests have been run and are passing, and you're happy with the state of things...

  1. Create a branch named release
  2. Update ReleaseNotes.md, following the existing format
  3. Bump the version number in Directory.build.props and appveyor.yml
  4. Push the branch to GitHub and create a pull request
  5. If the build succeeds, accept the pull request
  6. Create and push a tag from the new HEAD git tag v#.#.# and git push --tags
  7. Create the NuGet packages (in the local solution root) for the new version: dotnet pack --output ..\
  8. Test the NuGet packages! How to install NuGet package locally
  9. Create a new release using the tag you just created and pasting in the release notes you just wrote up. Attach a copy of the latest .nupkg files generated above.
  10. Push the new packages up to NuGet dotnet nuget push