fix: wireguard unknown revision when using GOPROXY=direct#9620
Merged
fix: wireguard unknown revision when using GOPROXY=direct#9620
Conversation
Contributor
Looks like new artifacts were built from this PR. Get them here!Artifact URLs |
ssoroka
approved these changes
Aug 17, 2021
reimda
pushed a commit
that referenced
this pull request
Aug 19, 2021
(cherry picked from commit 967e31e)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolve: #8800
Relevant information that explains the problem:
Seems this issue only happens when GOPROXY is set to direct, I created pr to implement the workaround suggested by the above links to use the pseudo version number for wireguard.
For more information on pseudo versions you can look here: https://golang.org/doc/modules/version-numbers#tmp_1
This is also causing dependabot to fail.