You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently a CVE for protobuf-java:jar:3.23.4 which I would like to highlight.
But the problem is also the following:
From the developers of opentelemetry-proto-java, it seems that (I am just quoting):
unfortunately it looks like this artifact io.micrometer:micrometer-registry-otlp didn't follow [our guidance](https://github.com/open-telemetry/opentelemetry-proto-java#support):
We have no intention of eventually publishing stable artifacts. If you need guarantees, please generate your own bindings, consulting [grpc codegen](https://grpc.io/docs/languages/java/generated-code/#codegen) and possibly [build.gradle.kts](https://github.com/open-telemetry/opentelemetry-proto-java/blob/main/build.gradle.kts)
Thank you for the issue!
Lets continue the discussion on #5658. We also need to discuss our options internally.
Regarding the quote above, I think it worths to mention that it seems the readme was clarified yesterday(7f3d19c) and a note about this was added earlier this year (e2efe5f). Before that, the readme only contained how to use the published artifact publicly available in Maven Central. We added OTLP support back in 2022 where there was no sign that this artifact should not be used. As of today, Maven Central does not have any note that users should not use these artifacts, neither the javadoc of the published sources. The artifact name does not indicate that it is not intended for eventual production use either and/or it should be only used by OTel test suites.
Hello team,
Just wanted to reach out regarding a small issue.
The background is that there is this chain of dependencies:
There is currently a CVE for protobuf-java:jar:3.23.4 which I would like to highlight.
But the problem is also the following:
From the developers of opentelemetry-proto-java, it seems that (I am just quoting):
open-telemetry/opentelemetry-proto-java#19 (comment)
If this is the case, and it seems the underlying library is not "stable", can micrometer decouple from this unstable dependency?
Thank you for your time on this issue.
The text was updated successfully, but these errors were encountered: