Fails to get last tag

For some reason semantic release is getting the last release tag incorrectly.

In my case it gets v27.5.0 when the last version is v27.5.1, which is correctly pushed in GitHub repository. Later the release fails because the packages tries to push v27.5.1 but it already exists.

We had to move to manual releases just because of this, and there’s apparently no way to break this missed release cycle. I’m pretty sure this is a bug on this utility but couldn’t figure out which one, and sadly I can’t provide much more details since the repo and packages are private.

[pvdlg]

The output might depends in the version of git you are using. To be sure check the exit code of that command.

git merge-base --is-ancestor v27.5.1 master
echo $?
// => Return 0 if in history, something else otherwise

[jeremenichelli]

Cool, yeah I just re-pushed the tag and the return value is 0, hope this fixes our next release. I’ll come here later to confirm if this solved the solution, also it would be good if you had a troubleshooting document for this type of cases so we don’t bother you that much. I would love to contribute but I don’t have enough knowledge to do it.

Thanks again for your help @pvdlg.