Skip to content

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

Not planned
@gopherbot

Description

@gopherbot

@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.

Activity

added this to the Go1.20.13 milestone on Dec 6, 2023
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][/+] on Dec 6, 2023
modified the milestones: Go1.20.13, Go1.20.14 on Jan 9, 2024
modified the milestones: Go1.20.14, Go1.20.15 on Feb 6, 2024
dmitshur

dmitshur commented on Mar 28, 2024

@dmitshur
Member

Go 1.20 has exited its support window per https://go.dev/doc/devel/release#policy.

locked and limited conversation to collaborators on Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @dmitshur@gopherbot

        Issue actions

          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] · Issue #64585 · golang/go