docs: update release process to check dependencies within workspace

Also add the new crate to `RELEASE.md` so it's not overlooked.

Sponsored-by: pep.foundation

1 files changed, 7 insertions, 4 deletions

diff --git a/RELEASE.md b/RELEASE.md
index 5798a45..08041b3 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -9,6 +9,7 @@ file with release notes, and only one set of Debian packaging (only
 the binaries and template resources are packaged). The crates are,
 currently:
 
+- `subplot-build`
 - `subplotlib-derive`
 - `subplotlib`
 - `subplot`
@@ -22,16 +23,18 @@ git ls-files | grep Cargo.toml
 Do these for each crate, with leaf crates in the dependency tree
 first:
 
-1. Run `cargo update` and `cargo outdated` for the crate, and make any
+1. Check that the dependency versions on any other Subplot crates are
+   correct.
+2. Run `cargo update` and `cargo outdated` for the crate, and make any
    needed updates.
-2. Review changes in the crate (`git log -p .` in the crate's
+3. Review changes in the crate (`git log -p .` in the crate's
    sub-directory). Update the top level `NEWS.md` with any changes
    that users of Subplot need to be aware of.
-3. Update the crate's `Cargo.toml` with the appropriate version number
+4. Update the crate's `Cargo.toml` with the appropriate version number
    for the new release, if there's been any changes. If any of the
    other crates depend on this crate, update their dependency
    information in their `Cargo.toml` as needed.
-4. Run `cargo publish --dry-run` and fix any problems.
+5. Run `cargo publish --dry-run` and fix any problems.
 
 For the top crate `subplot` additionally do the following: