We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
this is related to #923
The text was updated successfully, but these errors were encountered:
I think we do not need to do anything special to release to gopkg.in. Taking a look at this page. There are two URL patterns supported:
gopkg.in/pkg.v3 → github.com/go-pkg/pkg (branch/tag v3, v3.N, or v3.N.M) gopkg.in/user/pkg.v3 → github.com/user/pkg (branch/tag v3, v3.N, or v3.N.M)
This is something we already follow this. Therefore, the following should work out well:
gopkg.in/urfave/cli.v1 -> v1 branch or v1.x.x release tags gopkg.in/urfave/cli.v2 -> v2 branch or v2.x.x release tags
This would work very well for those not using Go Modules. I have also managed to reproduced this :
Code Setup
Output for v1
Output for v2
Sorry, something went wrong.
I had disabled Go Modules for above project and instead used the project folder as the GOPATH
GOPATH
Got it, so it sounds like people who want to download the package from gopkg.in are currently 100% capable of doing so 👍 So I'll close this ♻️
No branches or pull requests
this is related to #923
The text was updated successfully, but these errors were encountered: