Repository navigation
Bump version to 2.1.1 - #117
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MYpyLV58pZcMLGRjaUKNBX
jrothrock
approved these changes
Oct 13, 2026
Contributor
|
@jrothrock @quinnmil Is there any time expectation you can share for when this will be published to rubygems? It also looks like |
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
3 participants
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.
Patch release for the fix in #114, which closes #115. With
opentelemetry-logs-sdk>= 0.7.0, every log export failed and all logs were silently dropped.ScoutApm::Logging::VERSIONto2.1.1CHANGELOG.mdFollow-up (not in this release): #116, where log severity numbers will be wrong once
opentelemetry-exporter-otlp-logsships open-telemetry/opentelemetry-ruby#2434.