-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Last published version of io.opentelemetry.semconv:opentelemetry-semconv #44
Comments
As I understand it, the "publication mechanism" is always triggered by a human, so it probably just hasn't been kicked off yet. |
I'm blocking the 1.24.0 release on resolving #41 and #40. The process for releasing currently requires a very manual and error process process to retain any attributes that were removed from the semantic conventions with a However, #40 and #41 resolve these open questions with solutions that have been discussed and agreed on in various Java SIG meetings. Given that we have a path forward, and PRs in place to achieve it, we should take that route rather than continuing with the old process. |
I see. Thanks for the explanation and good luck with automating the release process to get there. 💪 |
Thanks a lot for unblocking the release and doing a new one! We are about to consume it now. 🙂 |
Hello,
I am following what's described in opentelemetry-java 1.31.0 release notes:
When I look at the releases of open-telemetry/semantic-conventions, the last release is
1.24.0
, and yet, when I go to maven central, the only release I can find is1.23.1-alpha
.Since it is supposed to be "published in lockstep", I was expecting to find
1.24.0
in maven central.Did I misunderstand something or is the publication mechanism broken?
Thanks
The text was updated successfully, but these errors were encountered: