Now go mod requires to have prefix "v" for it's tag in VCS and it's mandatory so you can't use tags in form of "A.B.C" in your workflow. But this limitation has little to zero reason to exist so why is it strict requirement? Why not to allow use both "vA.B.C" and "A.B.C" tags? Who are using "A.B.C" tags for anything but version? It can be done without modifying current .mod files by just ignoring "v" prefix during repository search.
Many teams use prefix-less tags for versions (both for Go before modules and non-Go projects). Not to mention that it's not a valid semver <https://github.com/semver/semver/blob/master/semver.md#is-v123-a-semantic-version> (but very common though) and thus requirement even less understandable. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
