-
Notifications
You must be signed in to change notification settings - Fork 304
Release Process
This wiki describes how we release a new version to the public.
-
Update the
CHANGELOG.md
file, and then push it to the master (after peer review) -
When you're ready to release in your local system checkout and pull the latest changes of the
master
branch -
Then run the following command based on the type of the release, this will create a commit and tag that commit with
vx.y.z
sem. ver., based on the flag passed to the command.Release Type Command Patch yarn version --patch
Minor yarn version --minor
Major yarn version --major
-
You can now push the commit using this command
$ git push origin master
-
You have to push the tag too, so that the CI can kicks in and deploy the extension to the Marketplace and also release under github releases tab
To release to the marketplace you need to renew the Azure pipeline token once every year and set it to the secrets on github repository settings