[connector,exporter,processor,internal/datadog] Bump opentelemetry-mapping-go to v0.13.2 #31019
Conversation
This file contains 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
…pping-go to v0.13.2
github-actions
bot
added
cmd/configschema
github-actions
bot
requested review from
dineshg13,
dmitryax,
liustanley,
mackjmr,
pmcollins and
songy23
mx-psi
force-pushed
the
mx-psi/update-v0.13.2
branch
from
0fa652c
to
2f90aab
Compare
songy23
approved these changes
Feb 2, 2024
codeboten
approved these changes
Feb 2, 2024
anthoai97
pushed a commit
to anthoai97/opentelemetry-collector-contrib
that referenced
this pull request
Feb 12, 2024
…pping-go to v0.13.2 (open-telemetry#31019) Updates opentelemetry-mapping-go to v0.13.2 **Link to tracking Issue:** Fixes DataDog/opentelemetry-mapping-go/issues/252
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.
Description:
Updates opentelemetry-mapping-go to v0.13.2
Link to tracking Issue: Fixes DataDog/opentelemetry-mapping-go/issues/252