You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2023. It is now read-only.
thanks for confirming. This issue is caused by mixing different versions of the same packages to support backward compatibility with old build approaches. We're working on getting rid of these dependencies but it takes a bit more than we expected so for now there are two alternatives to go get:
get binaries from the latest release - we're keeping it in sync with the upstream
git clone, go install - if you want to have your version of tm CLI installed
Outdated dependencies and mixed versions are not the reason for a failing go get - in this PR we got rid of old components and it didn't help.
What actually caused the described issue is go get behavior:
replace directives have no effect outside of your own module, so if you invoke go get outside of your own module, they have no effect.
In other words, it means that dependency replacements that we have in go.mod are not honored if you run go get github.com/triggermesh/tm outside the module root path. We've updated the readme to avoid this issue:
user reported that he had a build errors when run
go get github.com/triggermesh/tm
command:The text was updated successfully, but these errors were encountered: