From cf5878a4b36d65e7e9588176bee8398f8346325d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Wed, 6 Apr 2022 21:01:28 +0200 Subject: [PATCH] chore: update release steps in CONTRIBUTING.md --- CONTRIBUTING.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c22a166eb3..23e33b8813 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -62,7 +62,7 @@ The controller takes care of the following: ## Creating a release In order to produce a release you will need to be a Unleash core team member and have the Unleash admin role assigned on the Unleash organization on GitHub. -# Step 1: create a new version tag +### Step 1: create a new version tag Use npm to set the version in package.json and specify a version tag. @@ -77,4 +77,12 @@ This command will trigger an internal verification step where we will perform th - *STEP 3. Build* - Validate that we are able to build the project - *STEP 4. Test* - Validate that all test runs green. -If all steps completes a single commit is produced on the main branch where the `version` property in package.json is updated, and a git tag is created to point to that tag specifically. \ No newline at end of file +If all steps completes a single commit is produced on the main branch where the `version` property in package.json is updated, and a git tag is created to point to that tag specifically. + +### Step 2: push tag + +```sh +git push origin main --follow-tags +``` + +This will push the new tag and a GitHub action will trigger on the new version tag, build the release and publish it to npm.