chore: update release process & include generated CLi version script (#…

…302)

CONTRIBUTING.md

@@ -66,4 +66,20 @@ When naming the title of your pull request, please follow the [Conventional Comm
 guide. 
 
 Please also enable **“Allow edits by maintainers”**, this will help to speed up the review
-process as well.
+process as well.
+
+
+### Run a release...
+
+1. Switch to `main` branch locally.
+2. Run `git pull origin main`.
+3. Run `git pull --tags` to make sure all tags are fetched.
+4. Create new branch with the signature "release/[year]-[month]-[day]".
+5. Push your branch to git running `git push origin [RELEASE BRANCH NAME]`.
+6. Run `melos version` to automatically version packages and update Changelogs.
+7. Run `melos publish` to dry run and confirm all packages are publishable.
+8. Run `melos cli-version` to generate the latest version number for the CLI & commit.
+9. Run `git push origin [RELEASE BRANCH NAME]` & open pull request for review on GitHub.
+10. After successful review and merge of the pull request, switch to `main` branch locally, & run `git pull origin main`.
+11. Run `melos publish --no-dry-run` to now publish to Pub.dev.
+12. Run `git push --tags` to push tags to repository.

melos.yaml

@@ -38,4 +38,4 @@ scripts:
         - flutterfire_cli
 
   format: dart format -o write .
-  version: dart run scripts/generate_version.dart && git add packages/flutterfire_cli/lib/version.g.dart
+  cli-version: dart run scripts/generate_version.dart && git add packages/flutterfire_cli/lib/version.g.dart