-
Notifications
You must be signed in to change notification settings - Fork 11
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
go-resty import requires replacement propagation #2
Comments
Changed it to: |
Still having issues with replacement propagation.
|
Ah I see. This does not appear to be an issue on go 1.13.4. |
@kevingentile I commited the changes after go mod tidy. |
@jamesdickson6 Thanks for taking another look. Yeah, I'm still running into issues. I can copy the replacement line into my Related issues: I've created a sample app targeting go 1.13 and 1.14 you can find here |
The repo has been upgraded to go 1.14 and resty v2. I think this issue is gone now. |
Scenario
Import
morepheus-go-sdk
into a project and tidy modules. Task fails due to invalid mapping of indirect dependency. The existing import targetsv1.12
but the replacement points tov1.11
. Workaround is to propagate the replacement in the downstream project.Failed build
go.mod
Valid build
go-resty
documentation states modules are supported from go v1.10+ but this appears to be misleading. May want to entertain upgrading to V2.Replacement target
The existing module replacement is pointing to
v1.11
of go-resty as the target for the import ofv1.12
:should be
The text was updated successfully, but these errors were encountered: