I just encountered this bug on a recent project. However, having performed several successful releases on other projects in the past, I was intrigued why the issue has occurred. I had initially assumed it was because I moved to v2.4 and the other successfully tagged projects had used v2.2.1. However, when I enforced v2.2.1 on my failing project, the issue still occurred.
Rolling back to v2.1 solved the problem for me also. However, it does nothing to help explain why other projects have been tagged correctly using v2.2.1.