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

Fix version in go.mod file #813

Closed
wants to merge 1 commit into from
Closed

Conversation

kolaente
Copy link

Fixes #812

@mattn
Copy link
Owner

mattn commented May 15, 2020

You can upgrade with go get -u github.com/mattn/go-sqlite3.

See #755

@mattn mattn closed this May 15, 2020
@kolaente
Copy link
Author

@mattn I tried that, it did not upgrade. I still have github.com/mattn/go-sqlite3 v2.0.3+incompatible in my go.mod file.

@mattn
Copy link
Owner

mattn commented May 15, 2020

How about this?

go get -u github.com/mattn/go-sqlite3@v2.0.5

@kolaente
Copy link
Author

Gives me the error mentioned in #812:

$ go get -u github.com/mattn/go-sqlite3@v2.0.5
go: finding github.com/mattn/go-sqlite3 v2.0.5
go get github.com/mattn/go-sqlite3@v2.0.5: github.com/mattn/go-sqlite3@v2.0.5: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

@mattn mattn reopened this May 15, 2020
@vtolstov
Copy link

you have only 3 ways

  • update go.mod to have /v2 and users must use /v2 to their import paths for never features
  • drop go.mod stuff
  • create v2 dir and copy files to it and commit

@coveralls
Copy link

coveralls commented May 15, 2020

Coverage Status

Coverage remained the same at 53.404% when pulling 8b782e1 on kolaente:fix/version-2 into db4c942 on mattn:master.

@mattn
Copy link
Owner

mattn commented Jun 18, 2020

I tagged v1.14.0 for latest release. If you are using v2.0.3, please use v1.14.0 instead.

See #812 (comment)

@mattn mattn closed this Jun 18, 2020
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

Successfully merging this pull request may close these issues.

Can't upgrade to version 2.0.5
4 participants