Protobuf: Getting a deprecation warning message?

[aaabhilash97]

Any idea why I'm getting this warning message?.

WARNING: Package "github.com/golang/protobuf/protoc-gen-go/generator" is deprecated.
    A future release of golang/protobuf will delete this package,
    which has long been excluded from the compatibility promise.

Running these commands

protoc \
        --proto_path=api/proto --proto_path=third_party/include \
        --proto_path=third_party/ --grpc-gateway_out=logtostderr=true:pkg/api \
          $(PROTO_ENTRY);

 protoc \
        --proto_path=api/proto --proto_path=third_party/include \
        --proto_path=third_party/ --grpc-gateway_out=logtostderr=true:pkg/api \
          $(PROTO_ENTRY);

[dsnet]

The "github.com/golang/protobuf/protoc-gen-go/generator" package is the internal implementation of protoc-gen-go and was never intended for users to depend on. The reason it is publicly available is because the concept of an internal package was not introduced until go1.4. Even though the internal package mechanism did not exist back then, we have still documented that this package should not be used by users.

You're seeing the warning because either you are directly depending on the generator package or something you depend on is depending on the generator package. I recommend that you find out what is directly using the generator package and tell them to migrate to the protogen package or to fork the generator package and depend on their own local fork.

[aaabhilash97]

Thanks to @dsnet .
Package github.com/grpc-ecosystem/grpc-gateway using generator package internally.

[adi69]

Thanks to @dsnet .
Package github.com/grpc-ecosystem/grpc-gateway using generator package internally.

Fix for this was merged https://github.com/grpc-ecosystem/grpc-gateway/pull/1260 and released in the version https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.14.5

[adranwit]

Could you please silence this warning, annotation, and lack of that dependency in the future would be good enough trigger to address it, I have many 3rd party dep, it is almost impossible to get rid of that message. Once it's broken all 3rd part-owner address the issue I would think. For now, any new release of my CLI is coming with this message, really messed up.