-
Notifications
You must be signed in to change notification settings - Fork 435
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
proposal: move away from gopkg.in as the canonical import path #848
Comments
This issue is still open I think? Sorry to hear about the |
My colleague @ajgajg1134 just pointed out that this might be related to golang/go#57185 |
This issue is still open I think?
Sorry, you're right. I must have confused the issues.
|
My colleague @ajgajg1134 just pointed out that this might also be related to golang/go#57185
Thanks! Yes that was probably it. I was trying to update dd-trace-go and immediately went down the gopkg.in route finding this issues.
|
Fixed in #2300 (for v2, not released yet) |
Given the fact that we've now switched to modules, it should no longer be necessary to use
gopkg.in
for import paths as a dependency and we can leave it atgit.luolix.top
The text was updated successfully, but these errors were encountered: