go-github: Including version number in module path breaks Go modules
Including the version number, e.g. v26, in the module path breaks Go modules as v25 was deleted.
See https://github.com/twpayne/chezmoi/pull/355 for an example of this breaking a project.
Please consider removing the version number from the path and using Go modules as Russ intended 😃
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (7 by maintainers)
I think I messed up here. Big apologies for the noise and distraction. Please re-open if I missed something.
It’s possible that I’ve made a mistake here. It looks like
github.com/google/go-githubis following the releasing modules (v2 or higher) strategy described in the Wiki, and it’s possible that the triggering issue hit problems because the user’s Go version does not support this. I’ll ask.