Merge pull request #279 from Sh3Rm4n/fix-release

Set correct cargo release push remote

Author: Sh3Rm4n

RELEASE_PROCESS.md

@@ -2,12 +2,18 @@
 
 1. Ensure all notable changes are in the changelog under "Unreleased".
 
-2. Execute `cargo release <level>` to bump version(s), tag and publish
+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`.
 
-3. Go to the GitHub releases, edit the just-pushed tag. Copy the release notes
-   from the changelog.
+4. Go to the GitHub releases, edit the just-pushed tag. Copy the release notes
+   from the [changelog](CHANGELOG.md).
+   - Remove the brackets from the PR numbers, as these are not needed for
+   GitHub's release notes.

release.toml

@@ -2,7 +2,8 @@
 
 tag-message = "{{version}}"
 no-dev-version = true
-pre-release-commit-message = "Release {{version}}"
+pre-release-commit-message = "Release v{{version}}"
+push-remote = "upstream"
 
 # Change the changelog's `Unreleased` section to refer to this release and
 # prepend a new `Unreleased` section