Creating Tagged Releases of wskdeploy

The most convenient way to create a tagged release for wskdeploy is to build the binaries by adding tag to upstream master.

1. Add a tag to a commit id: git tag -a <tag/version> <commit hash>

for example, using the (7 min.) leading characters on commit hash:

$ git tag -a 0.8.9 c08b0f

2. Push the tag upstream: git push -f upstream <tag/version>

for example:

$ git push -f upstream 0.8.9

Travis will start the build of 0.8.9 automatically by the event of tag creation.

If the travis build passed, binaries will be pushed into releases page.

If we modify the tag by pointing to a different commit, use git push -f upstream 0.8.9<tag> to overwrite the old tag. New binaries from travis build will overwrite the old binaries as well.

You can download the binaries, and delete them from the releases page in GitHub if we do not want them to be public.

Publishing Tagged Release to Homebrew

Homebrew is used to install wskdeploy locally. Once we release a new version of wskdeploy we should update its version in homebrew.

Get the new release SHA256 checksum by downloading the Source Code (tar.gz) from the releases page and running shasum -a 256 X.Y.Z.tar.gz on the tarball.

Update brew formula with the automation command brew bump-formula-pr:

$ brew bump-formula-pr \
  --url='https://github.com/apache/openwhisk-wskdeploy/archive/X.Y.Z.tar.gz' \
  --sha256='PASTE THE SHA256 CHECKSUM HERE' \
  --version='X.Y.Z' \
  wskdeploy