cmd/go: do not treat branches with semantic-version names as releases #35671
Labels
Milestone
Comments
See #29731, which also involves confusion between branches and versions. |
Any updates on this? I think this is a very scary issue, since if a collaborator created a vN branch deliberately or not once, the repository's versioning would be corrupted forever... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#33558 (comment) reports a situation in which a
v2.0.0
branch was created and subsequently removed, butproxy.golang.org
cached av2.0.0+incompatible
release.If someone creates a branch named
v2.0.0
, they probably intend for that branch to contain the development leading up tov2.0.0
, not for that branch as first published to be the definitive final release ofv2.0.0
. Thego
command should not mistake the former for the latter.CC @jayconrod @mattn @thepudds
The text was updated successfully, but these errors were encountered: