-
Notifications
You must be signed in to change notification settings - Fork 24
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
SetRequire called with conflicting versions #24
Comments
If I downgrade the project and go to version 1.20.10 then it works. |
Haven't been able to make a simple reproduction. |
If you are able to, please feel free to post it. I'll try to reproduce it myself if/when I get some free time. Thanks for reporting! |
I managed to make a minimal repro it seems. Try https://github.com/HenrikPoulsen/mod-setrequire-repro To reproduce I used the following docker command
Hope this helps and you are able to reproduce it without any issues. |
I am also experiencing this same issue:
It was working until recently, which makes me think it is new to 0.6.0 or 0.7.0. We are also using Go 1.21, but we upgraded a couple of months ago and this is the first time I recall seeing this. |
Thank you @HenrikPoulsen for the repro. The reason this was failing is because your go.mod file already contained gopkg.in/yaml.v3 I imagine this is also why @oschwald saw a similar error, assuming their go.mod file already contained the .../oapi-codegen/v2 module. I pushed a fix here: 2a21052 And created v0.7.1 release, if this bug continues to persist please re-open the issue. Thanks! PS. It might be worth adding tests for this issue. |
I am using Renovate which uses mod.
I am getting the following in both Renovate as well as locally:
I am not really finding anything online indicating that others have had this issue before.
Any idea what might cause this?
The text was updated successfully, but these errors were encountered: