[backend] missing 'v' prefix in repo tags

When trying to use the go client in github.com/kubeflow/pipelines/backend/api/go_client, I find that go mod can’t fetch the corresponding tags in this github repo, because all tags defined are missing the ‘v’ prefix and are considered non-canonical tag formats.

E.g., tag ‘1.5.1’ should be ‘v1.5.1’.

[Bobgy]

Also found that python package version should not have the ‘v’ prefix either: https://www.python.org/dev/peps/pep-0440/.

I feel that we should only add the ‘v’ prefix on git tags, but avoid it in other cases. It might take quite some trial and error to figure out which versions require the v prefix and which don’t.

@NikeNano I’m leaning towards reverting the PR and revisit it in the next release to delay resolving the problems we’ve seen. What do you think?

[Bobgy]

Added to release tracker