protoc-gen-go-grpc not fully supported 'edition 2024'

[Anveena]

NOTE: if you are reporting is a potential security vulnerability or a crash,
please follow our CVE process at
https://github.com/grpc/proposal/blob/master/P4-grpc-cve-process.md instead of
filing an issue here.

Please see the FAQ in our main README.md, then answer the questions below
before submitting your issue.

What version of gRPC are you using?

google.golang.org/grpc v1.78.0
protoc-gen-go-grpc 1.6.0

What version of Go are you using (go version)?

go version go1.25.6 linux/amd64

What operating system (Linux, Windows, …) and version?

Linux

What did you do?

If possible, provide a recipe for reproducing the error.

When I update to editions 2024 and generate files with (features)[https://protobuf.dev/editions/features/#preserving] , like the demo from this page

import option "google/protobuf/go_features.proto";
option features.(pb.go).api_level = API_OPAQUE;

import option "google/protobuf/cpp_features.proto";
option features.(pb.cpp).string_type=STRING;

I got this error

protoc-gen-go-grpc: unable to determine Go import path for "google/protobuf/cpp_features.proto"

Please specify either:
	• a "go_package" option in the .proto source file, or
	• a "M" argument on the command line.

See https://protobuf.dev/reference/go/go-generated#package for more information.

--go-grpc_out: protoc-gen-go-grpc: Plugin failed with status code 1.

What did you expect to see?

No error, import option key words can be handled correctly

What did you see instead?

Same Above.

[arjan-bal]

Hi @Anveena, thanks for reporting this issue.

This error seems to be due to a missing go_package option in the cpp_features.proto file which is packaged with the protoc compiler. The protobuf Go plugin (protoc-gen-go) requires the go_package option to be set in every imported proto file. Since your file imports google/protobuf/cpp_features.proto, the requirement applies there as well. The go_features.proto file does have a go_package option set.

As a workaround, you can map the package manually using the -M flag in your protoc invocation:

--go_opt="Mgoogle/protobuf/cpp_features.proto=google.golang.org/protobuf/types/cppfeaturespb"
--go-grpc_opt="Mgoogle/protobuf/cpp_features.proto=google.golang.org/protobuf/types/cppfeaturespb"

However, I feel this workaround shouldn't strictly be necessary. I suggest filing an issue on the protobuf Go repository to get this fixed upstream.