followed instructions here
In master branch
git commit -am 'updated version to 1.3.4.1'
git tag v1.3.4.1
git push --tags origin master:master
however, this caused the circleci builds to end up in mauo-calvi/squiddio-beta and not in mauro-calvi/squiddio-prod, as expected. The appveryor builds were placed correctly in mauro-calvi/squiddio-prod.
Someone suggested it may be because a corresponding release was not available on github, so I tried
git commit -am 'updated version to 1.3.4.2'
git version v1.3.4.2 # creaded release 1.3.4.2 on github
git push --tags origin v1.3.4.2 # this did not trigger builds on circle ci
git push --tags origin master:master # this did, but they still ended up in the cloudsmith beta folder
I am sort of fumbling in the dark here...I am sure I am missing a step or two.
Also, upon inspection of the circleci logs, it looks like environmental variable BUILD_TAG in cloudsmith-upload.sh.in is NULL, which causes the upload to default to beta. That variable is set to CIRCLE_TAG in line 30, but can't figure out where this last variable is initialized..
followed instructions here
In master branch
however, this caused the circleci builds to end up in mauo-calvi/squiddio-beta and not in mauro-calvi/squiddio-prod, as expected. The appveryor builds were placed correctly in mauro-calvi/squiddio-prod.
Someone suggested it may be because a corresponding release was not available on github, so I tried
I am sort of fumbling in the dark here...I am sure I am missing a step or two.
Also, upon inspection of the circleci logs, it looks like environmental variable BUILD_TAG in cloudsmith-upload.sh.in is NULL, which causes the upload to default to beta. That variable is set to CIRCLE_TAG in line 30, but can't figure out where this last variable is initialized..