summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBryant Mairs <bryantmairs@google.com>2018-06-02 10:46:04 -0700
committerBryant Mairs <bryantmairs@google.com>2018-06-02 10:46:04 -0700
commit5f43cc83cb27712b87c6c4a93e944df1a637bcd9 (patch)
tree30705ab00ec11bceb47b99d86de6be2e85407bf1
parentb92b36fd5adfb42f27d7f7c1a4d9ec6f7a8d3625 (diff)
downloadnix-5f43cc83cb27712b87c6c4a93e944df1a637bcd9.zip
Update release procedure
It can be easy to miss something that's required for a release, so run cargo publish as a dry run to make sure everything's set.
-rw-r--r--RELEASE_PROCEDURE.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/RELEASE_PROCEDURE.md b/RELEASE_PROCEDURE.md
index 3429d130..f26b6197 100644
--- a/RELEASE_PROCEDURE.md
+++ b/RELEASE_PROCEDURE.md
@@ -20,6 +20,8 @@ The release is prepared as follows:
- In `Cargo.toml`, change the libc dependency to the latest version.
- In `README.md`, update the version in the Usage section to the new
version.
+- Confirm that everything's ready for a release by running
+ `cargo publish --dry-run`
- Make a pull request.
- Once the PR is merged, tag the merge commit, e.g. `git tag v0.8.3
$MERGE_COMMIT_SHA1`.