Skip to content

Commit

Permalink
Merge pull request #1826 from shepmaster/release-instructions
Browse files Browse the repository at this point in the history
Remove unneeded release step
  • Loading branch information
JohnTitor authored Jul 19, 2020
2 parents b17047f + 11e03e8 commit e38ca71
Showing 1 changed file with 3 additions and 6 deletions.
9 changes: 3 additions & 6 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,14 +53,11 @@ platform in this crate, the next step is to get that sweet, sweet usage from
crates.io! The only next step is to bump the version of libc and then publish
it. If you'd like to get a release out ASAP you can follow these steps:

1. Update the version number in `Cargo.toml`, you'll just be bumping the patch
version number.
2. Run `cargo update` to regenerate the lockfile to encode your version bump in
the lock file. You may pull in some other updated dependencies, that's ok.
3. Send a PR to this repository. It should [look like this][example], but it'd
1. Increment the patch version number in `Cargo.toml`.
1. Send a PR to this repository. It should [look like this][example], but it'd
also be nice to fill out the description with a small rationale for the
release (any rationale is ok though!)
4. Once merged the release will be tagged and published by one of the libc crate
1. Once merged, the release will be tagged and published by one of the libc crate
maintainers.

[example]: https://github.com/rust-lang/libc/pull/583

0 comments on commit e38ca71

Please sign in to comment.