When is the next planned release?

[easwars]

The latest release is close to 6 months old.

gRPC-Go has a dependency on the generated protos here, and we would like to pin our dependency to a release version instead of a commit hash, and therefore would really appreciate if a new release is cut.

There is already an open issue for 1.x here: #391, but I would at least like to see a v0.13.0 in the near future.

Thanks.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[easwars]

Is there any update on this? Thanks

[jh125486]

Envoy v1.31.0 has been released for two weeks... can we get a new tagged release for the control plane?

Would you accept a PR to auto tag this repo after the Envoy sync runs?

[valerian-roche]

We usually do not create releases of the control-plane tracking envoy versions. There is ongoing work to split the generated api as a sub-module that could track envoy releases (as well as remove the need to source the entire repository to just source the api part)

[jh125486]

We usually do not create releases of the control-plane tracking envoy versions. There is ongoing work to split the generated api as a sub-module that could track envoy releases (as well as remove the need to source the entire repository to just source the api part)

Let me know if you need any help... we use the protobuf-generated Go files in go-control-plane instead of submoduling Envoy and generating them ourselves. (Mostly because submodules don't have great devx and cause havoc in our CI/CD sometimes.)

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.