From dfd1e94ea3d17507bdd63dcdaea7923963d26fb3 Mon Sep 17 00:00:00 2001
From: Sahas Subramanian <sahas.subramanian@proton.me>
Date: Wed, 19 Nov 2025 15:07:14 +0100
Subject: [PATCH] Update CONTRIBUTING.md

Signed-off-by: Sahas Subramanian <sahas.subramanian@proton.me>
---
 CONTRIBUTING.md | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 416e368..655f928 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -6,11 +6,16 @@ These are the steps to create a new release:
 
 1. Get the latest head you want to create a release from.
 
-2. Update the `RELEASE_NOTES.md` file if it is not complete, up to date, and
-   remove template comments (`<!-- ... ->`) and empty sections. Submit a pull
-   request if an update is needed, wait until it is merged, and update the
-   latest head you want to create a release from to get the new merged pull
-   request.
+2. Update the version in `Cargo.toml` to the new version.  Without this,
+   the new release will be rejected by `crates.io`.
+
+   Along with this, update the `RELEASE_NOTES.md` file if it is not
+   complete, up to date, and remove template comments (`<!-- ... ->`)
+   and empty sections.
+
+   Submit a pull request if an update is needed, wait until it is
+   merged, and update the latest head you want to create a release
+   from to get the new merged pull request.
 
 3. Create a new signed tag using the release notes and
    a [semver](https://semver.org/) compatible version number with a `v` prefix,