feat(release): include version updates in dependency and source files

Author: apiad

.gemini/commands/release.toml

@@ -12,6 +12,9 @@ Follow these steps precisely:
 4.  **Propose Version:**
     - Propose a new version number with a brief rationale.
     - Use `ask_user` to confirm the version.
+    = Update the version in `package.json`, `pyproject.toml` or any other dependency configuration file, if it exists.
+    - Update the version in any relevant source files if necessary (e.g., `__version__.py`).
+    - Update the version in any relevant documentation files if necessary (e.g., `README.md`).
 5.  **Update CHANGELOG.md:**
     - **IMMEDIATELY** after the version is decided, update `CHANGELOG.md`.
     - Create a new entry for the version, summarizing all changes since the last release.
@@ -21,7 +24,8 @@ Follow these steps precisely:
     - If confirmed:
         - Create a commit for the release: `git add CHANGELOG.md && git commit -m "chore(release): version <new_version>"`.
         - Create a git tag: `git tag -a "v<new_version>" -m "Release v<new_version>"`.
-        - Propose pushing the tag to the remote if it exists.
+        - Push the tag to the remote if it exists.
+        - Propose using `gh release create` for GitHub releases, including the changelog entry as the release notes.
 
 Report the successful completion of the release and the new version.
 """