Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(contrib): fix release guide #12919

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -302,12 +302,12 @@ Some things to keep in mind before publishing the release:
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.
6. Run `melos version --no-git-tag-version` to automatically version packages and update Changelogs.
7. Run `melos publish` to dry run and confirm all packages are publishable.
8. Run `melos bom [optional-version]` to update the `VERSIONS.md` and `scripts/versions.json` files.
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 `master` branch locally, & run `git pull origin master`.
11. Run `melos publish --no-dry-run` to now publish to Pub.dev.
11. Run `melos publish --no-dry-run --git-tag-version` to now publish to Pub.dev.
12. Run `git push --tags` to push tags to repository.
13. Ping @kevinthecheung to get the changelog in Firebase releases.

Expand Down
Loading