KateGo520

Cannot get latest version: module contains a go.mod file, so module path should be github.com/xxjwxc/gormt/v3

3

## Background The `github.com/xxjwxc/gormt` uses [Go modules](https://github.com/golang/go/wiki/Modules) and the current release version is `v3`. And it’s module path is `"github.com/xxjwxc/gormt"`, instead of `"github.com/xxjwxc/gormt/v3"`. It must comply with the specification of...

Potential import collision: import path should be "gopkg.in/h2non/gock.v1", not "github.com/h2non/gock".

2

## Background The `h2non/gock` has already renamed it’s import path from "github.com/h2non/gock" to "gopkg.in/h2non/gock.v1". As [README](https://github.com/h2non/gock/blob/v1.0.7/README.md) of `h2non/gock` v1.0.7 said, downstream repos should use "gopkg.in/h2non/gock.v1" to get or import `h2non/gock`....

Potential import collision: import path should be "mvdan.cc/sh", not "github.com/mvdan/sh"

1

## Background I find that `mvdan.cc/sh` and `github.com/mvdan/sh` coexist in this repo： https://github.com/garetht/amanar/blob/master/go.mod （Line 14 & 25） ``` github.com/mvdan/sh v2.6.4+incompatible mvdan.cc/sh v2.6.4+incompatible // indirect ``` That’s because the `mvdan/sh` has...

Proposal: Please start using Semantic Versioning

10

I found that this project already [supports Go modules](https://github.com/elazarl/goproxy/blob/master/go.mod). But sadly, the [tags](https://github.com/elazarl/goproxy/tags) doesn't follow [Semantic Versioning](https://semver.org), which means that all tags of this project will be ignored by Go...

Cannot get latest version: module contains a go.mod file, so module path should be github.com/elliotchance/gedcom/v39

3

## Background The github.com/elliotchance/gedcom uses [Go modules](https://github.com/golang/go/wiki/Modules) and the current release stream version is **v39**. It must comply with the specification of "Releasing Modules for v2 or higher" available in...

Potential import collision: import path should be "go.mongodb.org/mongo-driver", not "github.com/mongodb/mongo-go-driver"

1

## Background I find that `go.mongodb.org/mongo-driver` and `github.com/mongodb/mongo-go-driver` coexist in this repo： https://github.com/longfellowone/field-services/blob/master/go.mod （Line 22 & 32） ``` github.com/mongodb/mongo-go-driver v1.0.1 go.mongodb.org/mongo-driver v1.0.1 // indirect ``` That’s because the `mongodb/mongo-go-driver` has...

Proposal: Please tag a new release and start using Semantic Versioning

3

I found that this project already [supports Go modules](https://github.com/romanyx/recaptcha/blob/master/go.mod). The latest version v1.1.1 committed on 16 Jul 2018, and if module user run "go get gopkg.in/romanyx/recaptcha.v1", the old version v1.1.1...

Canonical repo address is inconsistent with module path

4

The github.com/KillingSpark/sparkzstd repo used the module, but the module path is set to github.com/killingspark/sparkzstd. This means that the canonical github repo address now conflicts with canonical go import packages. It...

Errors you may encounter when upgrading the library

3

(The purpose of this report is to alert `requilence/integram` to the possible problems when `requilence/integram` try to upgrade the following dependencies) ## An error will happen when upgrading library _gin-gonic/gin_:...

Errors you may encounter when upgrading the library

6

(The purpose of this report is to alert `standup-raven/standup-raven` to the possible problems when `standup-raven/standup-raven` try to upgrade the following dependencies) ## An error will happen when upgrading library _mattermost/mattermost-server_:...