Remove go.mod to resolve ambiguous import issue #7783
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dbaileychess
approved these changes
Jan 19, 2023
|
Are you now done making go.mod changes? This change broke our builds yet again. |
|
Yes this will be the last change. Once a new release is cut the issue should be resolved and you can go back to using |
|
@ceejatec this should be fixed now let me know if you have still have any issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #7780
Introducing a go.mod file into the go sub-directory resulted in versioning issues for many clients. We should revert the change and figure out a better/safer way to introduce a go.mod file.
After removing the go.mod file we'll have to wait till the next release before the issue is resolved.