Skip to content

Missing v34 blocks the use of v35 #938

Closed
@pjbgf

Description

@pjbgf

Go does not seem to be able to use the newly created git2go v35 as a v34 does not exist.

$ go get -d github.com/libgit2/git2go
[module path "github.com/libgit2/git2go/v34" (and .../v35/go.mod does not exist) at revision v35.0.0](go: github.com/libgit2/git2go/[email protected]: go.mod has non-.../v35 module path "github.com/libgit2/git2go/v34" (and .../v35/go.mod does not exist) at revision v35.0.0)

EDIT: After digging into it further, I noticed that the Git tag v35 is pointing to a commit in which the Go module version is v34.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions