fix: add note about version to RELEASING

Author: gadomski

RELEASING.md

@@ -3,14 +3,15 @@
 1. Determine which package you're releasing
 2. Determine the next version, following [semantic versioning](https://semver.org/)
 3. Create a release branch: `git checkout -b release/{package}-v{version}`
-4. Update that package's CHANGELOG with:
+4. Update that package's `pyproject.toml` with the new version
+5. Update that package's CHANGELOG with:
    - A new header with the new version
    - A new link at the bottom of the CHANGELOG for that header
-5. `git push -u origin`
-6. Once approved, merge the PR
-7. `git checkout main && git pull && scripts/release {package}`
-8. Go to the draft release href provided by the script, update that Github release with information from the CHANGELOG, and publish it
-9. Github actions will automatically publish a new PyPI release
+6. `git push -u origin`
+7. Once approved, merge the PR
+8. `git checkout main && git pull && scripts/release {package}`
+9. Go to the draft release href provided by the script, update that Github release with information from the CHANGELOG, and publish it
+10. Github actions will automatically publish a new PyPI release
 
 > [!IMPORTANT]
 > You'll need to set up [.netrc authentication](https://pygithub.readthedocs.io/en/stable/examples/Authentication.html#netrc-authentication) to use `scripts/release`.