Skip to content

Release Process

Alex Gilleran edited this page Jan 6, 2020 · 10 revisions

-1. Check out a merge branch from the old release branch and align the version with new master:

git checkout release/<old release version>
git checkout -b merge/<old release version>
npx lerna publish --force-publish --skip-npm --skip-git #set the version to the new master version

Then use a text editor to search for the old version and replace it wherever necessary (usually in Chart.yaml, values.yaml) and commit using your git client of choice

  1. Merge master into the merge branch and raise a PR.
git pull origin master
git push
  1. Create a new release branch:
git checkout master
git fetch origin master
git reset --hard origin/master
git checkout -b release/<version>
  1. Bump the lerna version
npx lerna publish --force-publish --skip-npm --skip-git

The new version should end in -RCx, e.g. 0.0.51-RC1

  1. Search for the old version in text and replace it.

  2. Commit, then push the release branch to github.

git push --set-upstream origin release/<YOUR VERSION HERE>
  1. Tag with the version and push that too.
git tag vx.x.x-RCx
git push origin vx.x.x-RCx

Wait for Gitlab to build that and push it up to dockerhub. Meanwhile...

  1. Release the last version without -RC - repeat steps 2-5 but first checkout the old release branch:
git checkout release/<old version>
git pull
  1. Create a branch for the new master version and bump its version to the new prerelease
git checkout master
git fetch origin master
git reset --hard origin/master
git checkout -b bump-version
npx lerna publish --force-publish --skip-npm --skip-git #publish with a pre-release version like 0.0.50-0

Also do a search using a text editor then commit.

  1. Put a new version at the top of the CHANGES.md file

  2. Push new-master and PR it!