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.

Sign up for GitHub

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: deployment #1858

Merged
merged 1 commit into from
Mar 3, 2023
Merged

docs: deployment #1858

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions Deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,12 @@ We automated some parts of the release process to make things easier. This file
- Check and ensure the previous release branch `release/vX.Y.Z` was merged into `main`
- Check and ensure `main` was back-merged into `develop`
- Check and ensure you are working in the latest `develop` branch
- Run `npx lerna version` - this will:
- update the `version` in each `package.json`
- Run `yarn run version` - this will:
- update the `version` in each `package.json` and `manifest.json`
- create branch `release/vX.Y.Z`
- create tag `vX.Y.Z`
- push the tagged branch automatically
- Pushing a tagged branch triggers a release build action in GitHub
- push the branch and tag automatically
- Pushing a tag triggers a release build action in GitHub
- Wait for pipeline to create release containing the extension zip
- If the automatic npm publish failed, do it manually (ask Gerald)
- Create GitHub pull request to merge the new branch `release/vX.Y.Z` into `main`
Expand Down