Remove all shared internal code refs from zipkin exporter#8413
Open
jack-berg wants to merge 3 commits into
Open
Remove all shared internal code refs from zipkin exporter#8413jack-berg wants to merge 3 commits into
jack-berg wants to merge 3 commits into
Conversation
Contributor
|
jack-berg
commented
May 18, 2026
| "opentelemetry-exporter-logging", | ||
| "opentelemetry-exporter-logging-otlp", | ||
| "opentelemetry-exporter-prometheus", | ||
| "opentelemetry-exporter-zipkin", |
Member
Author
There was a problem hiding this comment.
This is the key line that verifies I covered everything. If I missed anything, this test would fail.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #7863.
Removes all shared internal code refs from
opentelemetry-expoter-zipkin.This facilitates the plan to stop publishing in mid 2026 while guaranteeing that old zipkin releases can continue to be used with more recent SDK releases without risk of runtime breakages.
Places where I had to make decisions:
opentelemetry-java-instrumentationafter this release.