docs: improve release process (#1332)

Author: matiasleyba

.release-please-config.json

@@ -25,6 +25,7 @@
     "site",
     ".release-please-manifest.json",
     ".release-please-config.json",
+    "CONTRIBUTING.md",
     "tool"
   ]
 }

CONTRIBUTING.md

@@ -126,27 +126,45 @@ dart fix --apply
 💡 **Note**: While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional work, tests, or other changes before your pull request can be accepted.
 
 
-### 🛠️ Release Process (Automated via `release-please-action`)
+### Release Process 🚀
 
-We use [`release-please-action`][release-please-action-link] to automate versioning and changelog generation.
+We use [`release-please-action`][release-please-action-link] to automate versioning and changelog generation, along with a GitHub workflow that automatically publish the CLI to pub.dev.
 
-- Every commit to `main` is analyzed using [Conventional Commits][conventional_commits_link].
-- When a commit indicates a version bump is needed, a **release PR** is automatically created or updated.
-- The release PR includes:
-  - An updated `CHANGELOG.md`
-  - A version bump in `pubspec.yaml`
-  - A version bump in `lib/src/version.dart`
-- Once the release PR is merged:
-  - A new Git tag is created.
-  - A GitHub release is published with the changelog.
+### How it works:
 
-#### 💡 Notes
+- 📌 **On Every Commit to main:**
+    - Commits are analyzed using [Conventional Commits][conventional_commits_link].
+    - If a version bump is needed, a **release PR** is automatically created or updated by [`release-please-action`][release-please-action-link].
+    - The **release PR** includes:
+        - An updated `CHANGELOG.md`
+        - A version bump in `pubspec.yaml`
+        - A version bump in `lib/src/version.dart`
 
-- Use `feat`, `fix`, or `BREAKING CHANGE:` in commit messages to trigger version bumps.
-- The release PR can be manually edited before merging.
-- The GitHub Action is configured in `.github/workflows/release_please.yaml`
-- release-please settings are defined in `.release-please-config.json` and `.release-please-manifest.json`
+    ##### 💡 Notes
 
+    - The GitHub Action workflow that automates the release process is configured in `.github/workflows/release_please.yaml`
+    - release-please settings are defined in `.release-please-config.json` and `.release-please-manifest.json`
+    - The release PR can be manually edited before merging.
+    - The release PR should be merged **ONLY** when a new release is needed.
+
+<br />
+
+- ✅ **When the Release PR Is Merged:**
+    - A new Git tag is created.
+    - A GitHub Release is published with the changelog.
+    - A new version of the cli is automatically published in pub.dev.
+
+    #### 💡 Notes
+
+    - The publishing process is automatically triggered when a version tag is created.
+    - The automated publishing workflow to pub.dev is defined in `.github/workflows/pub_publish.yaml`
+
+<br />
+
+This document provides a good summary of how it works and how we use it, but we recommend that you also read the official documentation of [Conventional Commits][conventional_commits_link], [Semantic Versioning][sem_ver_link], [Publishing Dart packages][dart_publishing_link] and [`release-please-action`][release-please-action-link].
+
+[dart_publishing_link]: https://dart.dev/tools/pub/publishing
+[sem_ver_link]: https://semver.org/
 [release-please-action-link]: https://github.com/googleapis/release-please-action
 [conventional_commits_link]: https://www.conventionalcommits.org/en/v1.0.0
 [bug_report_link]: https://github.com/VeryGoodOpenSource/very_good_cli/issues/new?assignees=&labels=bug&template=bug_report.md&title=fix%3A+