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

v2.x.x not follows to right versioning #21

Open
micshome opened this issue Mar 30, 2020 · 2 comments
Open

v2.x.x not follows to right versioning #21

micshome opened this issue Mar 30, 2020 · 2 comments

Comments

@micshome
Copy link

Cant import version 2.x.x to my project with go.mod
Error:

go mod vendor
go: errors parsing go.mod:  
require github.com/beeker1121/goque: version "v2.1.1" invalid: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

It want it to be github.com/beeker1121/goque/v2, or use only 1.x.x version
Example, how it was implemented in other project github.com/savsgio/atreugo
Thanks!

@bigobject
Copy link

meet the same problem

beautifulentropy pushed a commit to letsencrypt/boulder that referenced this issue May 26, 2021
Update goque to its latest commit, which is an actual go module:
beeker1121/goque@4044bc2...d618510
Unfortunately, it still requires a commit hash (rather than just
a version number) due to issue beeker1121/goque#21.

This removes the need for multiple indirect dependencies to be included
in our go.mod file. It also transitively updates goleveldb:
syndtr/goleveldb@714f901...v1.0.0
@Yxnt
Copy link

Yxnt commented Sep 8, 2022

@micshome @bigobject

add github.com/beeker1121/goque d618510128aff49b39efd28bd1c72a18ad563e94 to go.mod file then use go mod tidy to update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants