Gorka Lerchundi Osa

I agree with you all that these kind of breaking changes should be treated in a much more soft way. BUT, consider two things: * It's a personal project and...

@johanbrandhorst I finally took some time to sketch a [code snippet](https://github.com/grpc/grpc-go/issues/555#issuecomment-506865430) to make our use case work. It did, but I don't know if it's going to work after reading...

Correct, thanks for confirming. Although we found another issue with the combo grpc-gateway, grpc, port-sharing, cmux and persistent connections kept by a reverse proxy (envoy in this case). It seems...

> This is probably not the place, no. Maybe raise an issue against Envoy? Already asked in Envoy and it seems like nothing could be done there as it keeps...

> This is probably not the place, no. Maybe raise an issue against Envoy? There are several reasons: * We want to have one and only one container for both...

@clehene we took another completely different approach to solve this issue. Make a `proto` to `proto` shrinker which removes any extension/annotation before passing it to the `protoc` generator.

@fenos bitten by the same, I tried to create my own dev workspace in order to see if the problem comes from protobuf-js but the steps on the CONTRIBUTING part...

No rush, thanks for keeping us updated!

@ericchiang @rithujohn191 I know that it's preferable to let other specifications do the hard job but I think including this extension point would open up `dex` to wide variety of...

Same issue and interest here. But I wouldn't do anything until this is an automatic releasing process. Knowing that it's manual and therefore a best effort policy, we'll continue compiling...