Ahmet Alp Balkan
Ahmet Alp Balkan
This is currently intentionally not documented, as Krew doesn't manage and update itself when installed via Homebrew. We also have no control or release automation for Homebrew at the moment....
If you're building at a version that the project not yet supports, you can probably also disable vet?
I'm trying to understand wdym by > kubectl [...] has no idea where or how to access krew kubectl looks at `$PATH` to find plugins. So when you type `kubectl...
gPRC-go module is already updated to 1.65. And http/1.1 vuln doesn't impact grpc, so it's irrelevant.
It solves one problem but incompatible everywhere else (e.g. docker images, tarball releases). Do you think addressing this discrepancy on line 47 where `go install` mentioned would help instead?
Another solution might be to rename the module in `go.mod` (to have `_`).
I have a feeling like this will break go-get due to repo name mismatch, if not, it'll break users who were installing via go-get. What do you think?
Sadly changing the module name will break too many users. https://sourcegraph.com/search?q=context:global+go+install+github.com/grpc-ecosystem/grpc-health&patternType=standard&sm=1&groupBy=repo I don't think this is a huge problem. We can just say "if installed via `go install` the binary...
I think this is a little too much disruption to existing installations with little to no gain, sorry.
@ivanvc requires org member permissions, if you have them, please rerun the command on the PR.