-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
False
-
-
False
-
-
-
-
-
-
-
There have been several discussions about this topic over time:
JBEAP-29998- https://redhat-internal.slack.com/archives/C06J5GFTM34/p1744289287137549?thread_ts=1744181156.228949&cid=C06J5GFTM34
The issue is we inlude non final versions of some artifacts:
maven-repo-dir/maven-repository/io/opentelemetry/instrumentation/opentelemetry-instrumentation-annotations-support/2.8.0.alpha-redhat-00001/opentelemetry-instrumentation-annotations-support-2.8.0.alpha-redhat-00001.pom maven-repo-dir/maven-repository/io/opentelemetry/instrumentation/opentelemetry-runtime-telemetry-java8/2.8.0.alpha-redhat-00001/opentelemetry-runtime-telemetry-java8-2.8.0.alpha-redhat-00001.pom maven-repo-dir/maven-repository/io/opentelemetry/instrumentation/opentelemetry-instrumentation-api-incubator/2.8.0.alpha-redhat-00001/opentelemetry-instrumentation-api-incubator-2.8.0.alpha-redhat-00001.pom maven-repo-dir/maven-repository/io/opentelemetry/semconv/opentelemetry-semconv/1.25.0.alpha-redhat-00001/opentelemetry-semconv-1.25.0.alpha-redhat-00001.pom maven-repo-dir/maven-repository/io/opentelemetry/opentelemetry-api-incubator/1.42.1.alpha-redhat-00001/opentelemetry-api-incubator-1.42.1.alpha-redhat-00001.pom maven-repo-dir/maven-repository/io/opentelemetry/proto/opentelemetry-proto/1.3.2.alpha-redhat-00001/opentelemetry-proto-1.3.2.alpha-redhat-00001.pom
semconv 1.30, 31, ... , 1.37 has been released. We should update unless there is a reason that prevent us from updating. Otherwise customer may expect final version.
Same for the other non-final version, we need either an update or a explanation for customers.
Note: this may affect RN (customer needs to be aware) based on what artifact will be released as non-final.