Skip to content

RELEASE_PROCESS.md

Latest commit

 

History

History
19 lines (14 loc) · 805 Bytes

RELEASE_PROCESS.md

File metadata and controls

19 lines (14 loc) · 805 Bytes
Raw

What to do to publish a new release

  1. Ensure all notable changes are in the changelog under "Unreleased".

  2. Ensure that the upstream remote is called upstream. The default is usually origin. To change the remote name, call git remote rename origin upstream.

  3. Execute cargo release <level> to bump version(s), tag and publish everything. External subcommand, must be installed with cargo install cargo-release.

    <level> can be one of major|minor|patch. If this is the first release (0.1.0), use minor, since the version starts out as 0.0.0.

  4. Go to the GitHub releases, edit the just-pushed tag. Copy the release notes from the changelog.

    • Remove the brackets from the PR numbers, as these are not needed for GitHub's release notes.