When attempting to depend on rules_webtesting via go.mod (for the Go webtester library), adding a dep like github.com/bazelbuild/rules_webtesting v0.3.5 does not work; Go gives an error saying that the version doesn't exist. Dropping the v does not work either, as it's invalid.
It appears that after v0.2.0, the tagging scheme changed from vX.Y.Z to X.Y.Z.
There is a workaround for now, which is to depend on a pseudo-version (v0.0.0-TIMESTAMP-COMMIT) corresponding to the X.Y.Z commit, which for 0.3.5 is v0.0.0-20210910170740-6b2ef24cfe95
This workaround is ugly though, and most users (myself included) will probably not realize that when they add rules_webtesting with go get / go mod tidy etc., it will add an outdated version to go.mod (v0.2.0).
Can this repository be reverted back to the old tagging scheme? Or maybe publish two tags pointing to the same commit, v0.3.5 (for Go users) and 0.3.5 (for other purposes)?
When attempting to depend on
rules_webtestingviago.mod(for the Go webtester library), adding a dep likegithub.com/bazelbuild/rules_webtesting v0.3.5does not work; Go gives an error saying that the version doesn't exist. Dropping thevdoes not work either, as it's invalid.It appears that after
v0.2.0, the tagging scheme changed fromvX.Y.ZtoX.Y.Z.There is a workaround for now, which is to depend on a pseudo-version (
v0.0.0-TIMESTAMP-COMMIT) corresponding to theX.Y.Zcommit, which for0.3.5isv0.0.0-20210910170740-6b2ef24cfe95This workaround is ugly though, and most users (myself included) will probably not realize that when they add
rules_webtestingwithgo get/go mod tidyetc., it will add an outdated version to go.mod (v0.2.0).Can this repository be reverted back to the old tagging scheme? Or maybe publish two tags pointing to the same commit,
v0.3.5(for Go users) and0.3.5(for other purposes)?