Skip to content
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

Closed
JnRouvignac opened this issue Feb 6, 2024 · 4 comments · Fixed by #57
Closed

Last published version of io.opentelemetry.semconv:opentelemetry-semconv #44

JnRouvignac opened this issue Feb 6, 2024 · 4 comments · Fixed by #57

Comments

@JnRouvignac
Copy link

JnRouvignac commented Feb 6, 2024

Hello,

I am following what's described in opentelemetry-java 1.31.0 release notes:

BREAKING: Stop publishing io.opentelemetry:opentelemetry-semconv. Please use io.opentelemetry.semconv:opentelemetry-semconv:1.21.0-alpha instead, which is published from open-telemetry/semantic-conventions-java. The new repository is published in lockstep with open-telemetry/semantic-conventions. (open-telemetry/opentelemetry-java#5807)

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 is 1.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

@jkwatson
Copy link

jkwatson commented Feb 7, 2024

As I understand it, the "publication mechanism" is always triggered by a human, so it probably just hasn't been kicked off yet.

@jack-berg
Copy link
Member

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 @Deprecated annotation. We do this because of the open questions in #5, #6, and #22.

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.

@JnRouvignac
Copy link
Author

I see. Thanks for the explanation and good luck with automating the release process to get there. 💪
Cheers

@JnRouvignac
Copy link
Author

Thanks a lot for unblocking the release and doing a new one! We are about to consume it now. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants