From e3934ee69cf6153e856caa45aac1e8c70399da25 Mon Sep 17 00:00:00 2001 From: Sunil Arora Date: Wed, 23 May 2018 14:13:29 -0700 Subject: [PATCH] add instructions for publishing a release --- build/README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/build/README.md b/build/README.md index 372c13857..b38a168a6 100644 --- a/build/README.md +++ b/build/README.md @@ -11,3 +11,18 @@ container-builder-local --config=build/cloudbuild_local.yaml --dryrun=false --wr ``` You will find the build artifacts under `/tmp/w/dist` directory + +### Publishing a Release + +Here are the steps to publish a new release. + + - Figure out the next version (for ex. v1.0.3) to be released. + - Ensure that you are on master branch and is up-to-date with the remote upstream/master branch. Do the following if you are in doubt: + ``` + git checkout master + git fetch upstream + git rebase upstream/master + ``` + - Tag the repo by running `git tag -a -m " release"` + - Push the tag to `upstream` branch by running `git push upstream ` + - Thats it! The new tag will trigger a job in Google Container Builder and new release should appear in the releases page.