[librsvg: 1/5] Add a "cargo update" step to RELEASING.md

[Federico Mena Quintero <federico src gnome org>]

commit e840e2ebc6d94bf3c9235d79dd37a6ff4aefbac7
Author: Federico Mena Quintero <federico gnome org>
Date:   Thu Mar 18 10:22:46 2021 -0600

    Add a "cargo update" step to RELEASING.md

 RELEASING.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)
---
diff --git a/RELEASING.md b/RELEASING.md
index fe9e6e73..9002738b 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -4,8 +4,11 @@ Feel free to print this document or copy it to a text editor to check
 off items while making a release.
 
 - [ ] Refresh your memory with https://wiki.gnome.org/MaintainersCorner/Releasing
-- [ ] Increase the package version number in `configure.ac` (it may already be increased but not released; 
double-check it).
+- [ ] Increase the package version number in `configure.ac` (it may
+      already be increased but not released; double-check it).
 - [ ] Copy version number to `Cargo.toml`.
+- [ ] `cargo update` - needed because you tweaked `Cargo.toml`, and
+      also to get new dependencies.
 - [ ] Tweak the library version number in `configure.ac` if the API changed; follow the steps there.
 - [ ] Update `NEWS`, see below for the preferred format.
 - [ ] Commit the changes above.
@@ -15,7 +18,9 @@ off items while making a release.
 - [ ] `git push` the signed tag to gitlab.gnome.org/GNOME/librsvg
 - [ ] `scp librsvg-x.y.z.tar.xz master.gnome.org:`
 - [ ] `ssh master.gnome.org` and then `ftpadmin install librsvg-x.y.z.tar.xz`
-- [ ] If this is a `x.y.0` release, [notify the release team][release-team] on whether to use it for the 
next GNOME version via an issue on their `GNOME/releng` project.
+- [ ] If this is a `x.y.0` release, [notify the release
+      team][release-team] on whether to use it for the next GNOME
+      version via an issue on their `GNOME/releng` project.
 
 ## Version numbers