Closed jozefchutka closed 9 years ago
this happens when a new tag was created on repo that already exists in haxelib git folder. Make sure to do push
solution: you can re-run validation phase and tag will get recognized this time
resolved in 0.0.47
this happens when a new tag was created on repo that already exists in haxelib git folder. Make sure to do push