Skip to content

Latest commit

 

History

History
25 lines (19 loc) · 1.89 KB

releasing.md

File metadata and controls

25 lines (19 loc) · 1.89 KB

Deploying a new release

Requirements

Creating a new release and deploying the package to nuget are administrative tasks and require that you have/do the following:

  1. Admin access to the GitHub NuGet organization
  2. Admin rights to the octokit.net repository
  3. For any PRs that introduce generated model changes the model changes should be generated by the person releasing to validate that there were no accidental manual changes made to generated files. Follow the process that is detailed in the contributing doc.

Prepare the changeset & publish to nuget.org

  1. Create a branch from main and update the version node Octokit.GraphQL.nuspec with the next version.
  2. Push the branch to GitHub and create a pull request. This will kick off the CI builds to verify all of the changes in main.
  3. Test! This is when you might need to run the generator or tests or simply review the changes as a set.
  4. When you're satisfied with this release, create a tag git tag v#.#.#-beta. For example, to create a tag for 0.1.9-beta git tag v0.1.9-beta
  5. Push the tag to the server. git push --tags
  6. Merge the Pull Request with the version change.
  7. When the tag and branch is successfully merged, the publish workflow will run and build and push the package to nuget
  8. Verify that the package has been uploaded to nuget.org
  9. Create a new release using the tag you just created and click auto generate notes. Cleanup the notes up as you see fit
  10. Check "This is a pre-release" and click "publish release" 🎉