Update release instructions to safeguard against updating versions of wrong packages

Author: pirelenito

CONTRIBUTING.md

@@ -5,7 +5,7 @@ Currently the process of updating the version of the packages is mostly manual.
 - If there is a release branch (see **Release candidate** below) that hasn't been merged to `main` yet now is the time to do so.
 - Make sure that you are logged in into your `npm` account. Use the command `yarn npm login` on the project folder to do this.
 - While on the `main` branch.
-- Perform a search an replace on all "package.json" files from the old version to the new. (ex `0.1.4` to `0.2.0`).
+- Perform a search an replace on all "package.json" files from the old version to the new. (ex `0.1.4` to `0.2.0`). Ensuring it only affects packages doing the version bump.
 - Run `yarn` to update the lockfile.
 - Commit the changes with a message containing the new version (ex: `0.2.0`).
 - Create an annotated git tag by running `git tag -a v0.2.0` (replace with the version). The tag message can be the version again.