x/exp/cmd/gorelease: cannot verify consistency of existing tag #47532
Labels
modules
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Tools
This label describes issues relating to any tools in the x/tools repository.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
I use
gorelease
locally, it's a great tool to automatically apply semver rules and suggest new version numbers.What did you expect to see?
In addition to that, I would like to use it on CI (specifically: every time a new
v*
tag is pushed) in order to verify that this tag is consistent with the semantic versioning rules. This would allow us to catch cases where contributors forgot to rungorelease
before tagging a new release, and quickly act to avoid breaking downstream users when we used the wrong version number.What did you see instead?
There's no way to verify an existing version using
gorelease
. Runninggorelease
on the most recent tag (v0.x.y
) will just returnv0.x.y+1
, running it using the-base=v0.x.y-1
results in the error message "Can only suggest a release version when compared against the most recent version of this major: v0.x.y".The text was updated successfully, but these errors were encountered: