I see 1.75.0 has been announced however, at least one of the artefacts is 
missing.

The bazel central registry (BCR) is missing the 1.75.0 and this is having a 
knock-on effect on downstream dependencies where 1.75.0 is being offered as 
an upgrade but bazel users can't use it as it's not in the bazel registry.

Issue has been raised by the maintainer of rules-proto-grpc here but 
remains untriaged for the last 2 weeks: 
https://github.com/grpc/grpc/issues/40733

Given the github issue is missing untriaged labels I suspect this may not 
be visible to the maintainers and hence has been missed.

Could somebody confirm what the issue is, if 1.75.0 is expected shortly or 
if this is a permanent change?

Kind regards

Dan B

-- 
*This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you are not the named addressee you must not disseminate, distribute or 
copy this e-mail. Please notify us on [email protected] 
<mailto:[email protected]> immediately if you have received this e-mail 
by mistake and delete this e-mail from your system. If you are not the 
intended recipient you are notified that disclosing, copying, distributing 
or taking any action in reliance on the contents of this information is 
strictly prohibited.*

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/grpc-io/97684d83-25f1-476d-babd-5a68c21ace8cn%40googlegroups.com.

Reply via email to