Don't publish to crates.io yet (#281)

RELEASE.md

@@ -15,7 +15,7 @@ all versions are updated simultaneously in `cargo-workspace-version`. To use it
 to update to 0.0.4, for example:
 
     $ cargo install cargo-workspace-version $ cargo workspace-version update
-v0.0.4
+v0.0.5
 
 See the [source code](https://github.com/ava-labs/cargo-workspace-version) for
 more information on the tool.
@@ -25,10 +25,5 @@ more information on the tool.
 > the next step.
 
 To trigger a release, simply push a semver-compatible tag to the main branch,
-for example `v0.0.1`. The CI will automatically publish a draft release which
-consists of release notes and changes. Once this draft is approved, and the new
-release exists, CI will then go and publish each of the sub-project crates to
-crates.io.
-> ❗ Publishing a crate with the same version as the existing version will
-> result in a cargo error. Be sure to update all crates within the workspace
-> before publishing to crates.io.
+for example `v0.0.5`. The CI will automatically publish a draft release which
+consists of release notes and changes.