Automated semantic versioning for travis-ci or any other ci

semver.sh

#!/bin/bash

export SEMVER_LAST_TAG=$(git describe --abbrev=0 --tags 2>/dev/null)
export SEMVER_RELEASE_LEVEL=$(git log --oneline -1 --pretty=%B | cat | tr -d '\n' | cut -d "[" -f2 | cut -d "]" -f1)

#curl -o /tmp/hub.tgz https://github.com/github/hub/releases/download/v2.2.9/hub-linux-arm64-2.2.9.tgz
#tar -xvzf /tmp/hub.tgz -C /tmp

if [ -z $SEMVER_LAST_TAG ]; then
    >&2 echo "No tags defined"
    SEMVER_LAST_TAG="0.0.1"
fi

if [ -n $SEMVER_RELEASE_LEVEL ]; then
    git clone https://github.com/fsaintjacques/semver-tool /tmp/semver &> /dev/null
    SEMVER_NEW_TAG=$(/tmp/semver/src/semver bump $SEMVER_RELEASE_LEVEL $SEMVER_LAST_TAG)
    git tag $SEMVER_NEW_TAG &> /dev/null
    git push origin --tags &> /dev/null
    echo $SEMVER_NEW_TAG
else
    >&2 echo "No release level defined"
fi

exit 0

Very cool. I looked into semantic-release but that was for versioning npm deploys and I'm just interested in bumping the version in package.json and mostly corresponding Github tags. Do you have example of the .travis.yml config to incorporate this script or are you still using this?

@mikesparr: I used in the travis.yml like so:

anguage: python
cache: pip
sudo: required
script:
- echo "yes!"
branches:
  only:
  - next
after_success:
- curl https://gist.githubusercontent.com/lxhunter/9d4310462b6972a3f57b5f914543fd51/raw/semver.sh | bash

Is there any sort of special process you have to do to get this to work? Looks like the tags aren't getting pushed back to github in my repo...

@proegssilb: sorry just saw your comment... how may i be of help?

for all interested: i moved to https://github.com/semantic-release/exec for this

Is there any sort of special process you have to do to get this to work? Looks like the tags aren't getting pushed back to github in my repo...

hey, same is happening with me... how can i perform the same thing successfully?