-
Notifications
You must be signed in to change notification settings - Fork 117
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
Pinned go-autorest to v13.3.3 #211
Conversation
Azure/go-autorest version less than v12.0.0 causes ambiguous imports. Though it's not agola direct dependency, it causes problem when others use agola.io/agola as dependency. So pinning Azure/go-autorest to v1.13.3 to prevent this issue. See: Azure/go-autorest#414
6fc62dc
to
205f746
Compare
@cuonglm Usually this kind of dependency issues could be fixed on the final package and not in an upstream one. Can you provide a reproducer of your issue? We have some external components relying on the agola client and haven't see the issue you're reporting (please also note that the agola api is not stable). |
This only applies if external component also depends on
|
@cuonglm go-autorest is a dep of the k8s go client and not directly used by agola so it doesn't makes sense to pin it in agola go.mod. I created a test example that uses agola and go autorest as dependencies and it built without issues so I don't know which are the issues on your projects (do you have a simpler reproducer that doesn't require adding agola as a gitea dependency?) but I suppose you should just fix the auto rest version on your side. |
Azure/go-autorest version less than v12.0.0 causes ambiguous imports.
Though it's not agola direct dependency, it causes problem when others
use agola.io/agola as dependency.
So pinning Azure/go-autorest to v1.13.3 to prevent this issue.
See: Azure/go-autorest#414