Closed bleggett closed 1 year ago
Hello,
I believe someone accidentally added back the replace to the go.mod folder. If you look back to the go.mod file, then you can see it again.
The reason why I am opening this issue again is because I can't run the go install
command anymore on the latest tag.
This is the same bug as https://github.com/opcr-io/policy/issues/61 - but recently another
replace
directive was added ingo.mod
and the issue resurfaced, meaning people cannot install this CLI tool in the documented fashion.Suggestion: Add a CI step that tests
go install