Prior to this change, if the tool was ran on a repo with no tags (a new project for example) it would fail because there were no tags returned by githubs api.
This change fixes that by updating the builder so that an error is generated only if there are no tags and the --next-version flag has not been provided.
Prior to this change, if the tool was ran on a repo with no tags (a new project for example) it would fail because there were no tags returned by githubs api.
This change fixes that by updating the builder so that an error is generated only if there are no tags and the --next-version flag has not been provided.