When triggering a build on a tag, CircleCI attaches a different version number from the tag’s. I would expect the version number to match the one of the release’s tag.
For example:
- Create a release with tag ‘v1.1.0’
- CircleCI builds with version number 1.1.1
Obviously, I would expect the version number in step two to be 1.1.0 as well…
Some screenshots:
- Local deployment using Fastlane with correct latest tag version number: https://www.dropbox.com/s/xxzmpdefo54yubu/local_deployment_get_correct_latest_tag.png?dl=0
- CircleCI deployment with incorrect latest tag version number: https://www.dropbox.com/s/j7lktnkicsuspkx/circleci_deployment_incorrect_latest_tag.png?dl=0
