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: v2.0.0 needs a /v2 on the go.mod module #17502

Closed
wants to merge 1 commit into from

Conversation

nikgibbens
Copy link

Version 2.x requires a /v2 at the end of the module in go.mod.

When trying to import
github.com/influxdata/influxdb/v2 v2.0.0-beta.7
The error message
go: github.com/influxdata/influxdb/[email protected]: go.mod has non-.../v2 module path "github.com/influxdata/influxdb" (and .../v2/go.mod does not exist) at revision v2.0.0-beta.7
is received.

Closes #

Describe your proposed changes here.

  • CHANGELOG.md updated with a link to the PR (not the Issue)
  • Well-formatted commit messages
  • Rebased/mergeable
  • Tests pass
  • http/swagger.yml updated (if modified Go structs or API)
  • Documentation updated or issue created (provide link to issue/pr)
  • Signed CLA (if not already signed)

Version 2.x requires a /v2 at the end of the module in go.mod.

When trying to import
```github.com/influxdata/influxdb/v2 v2.0.0-beta.7```
The error message
```go: github.com/influxdata/influxdb/[email protected]: go.mod has non-.../v2 module path "github.com/influxdata/influxdb" (and .../v2/go.mod does not exist) at revision v2.0.0-beta.7```
is received.
@nikgibbens nikgibbens changed the title v2.0.0 needs a /v2 on the go.mod module fix: v2.0.0 needs a /v2 on the go.mod module Mar 31, 2020
@russorat
Copy link
Contributor

russorat commented Apr 3, 2020

@nikgibbens thanks for the contribution. could you sign the CLA while i find someone to review? https://influxdata.com/community/cla/

@russorat
Copy link
Contributor

russorat commented Apr 3, 2020

closes: #16872

@jsternberg
Copy link
Contributor

Thank you for your contribution. For us to make this change, we need to also rewrite all of the ways the import is used and we also need to perform that rewrite on our internal codebase that uses this one as a library.

We are going to do that process today starting in a few hours. Thanks for bringing this to our attention to keep us honest on this. We had been planning to do this for awhile, but just never pushed the button on the transition. I'm going to close this. The staging zone for merging this same change is in #17607.

@jsternberg jsternberg closed this Apr 3, 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.

3 participants