Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: spurious "v1.x.y is not a tag" error when a tag's commit was previously download without the tag [1.20 backport] #64585

Open
gopherbot opened this issue Dec 6, 2023 · 0 comments
Labels
CherryPickCandidate Used during the release process for point releases GoCommand cmd/go
Milestone

Comments

@gopherbot
Copy link

@bcmills requested issue #53955 to be considered for backport to the next 1.20 minor release.

@gopherbot, please backport to Go 1.21 and 1.20. This fixes a bug that is otherwise difficult for users to understand and diagnose, and the fix is relatively uninvasive.

@gopherbot gopherbot added CherryPickCandidate Used during the release process for point releases GoCommand cmd/go labels Dec 6, 2023
@gopherbot gopherbot added this to the Go1.20.13 milestone Dec 6, 2023
@bcmills bcmills changed the title cmd/go: Go 1.18.4 still complains "v1.x.y is not a tag" if the target (private?) module had been once downloaded before being tagged [1.20 backport] cmd/go: spurious "v1.x.y is not a tag" error when a tag's commit was previously download without the tag [1.20 backport] Dec 6, 2023
@gopherbot gopherbot modified the milestones: Go1.20.13, Go1.20.14 Jan 9, 2024
@gopherbot gopherbot modified the milestones: Go1.20.14, Go1.20.15 Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CherryPickCandidate Used during the release process for point releases GoCommand cmd/go
Projects
None yet
Development

No branches or pull requests

1 participant