opentelemetry: prepare for 0.16.1 release #1919
Closed
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
|
I think @hawkw has moved the release management to the |
hawkw
added a commit
that referenced
this pull request
Feb 11, 2022
# 0.17.1 (February 11, 2022) ### Added - `OpenTelemetryLayer` can now add detailed location information to forwarded events (defaults to on) ([#1911]) - `OpenTelemetryLayer::with_event_location` to control whether source locations are recorded ([#1911]) ### Changed - Avoid unnecessary allocations to improve performance when recording events ([#1917]) Thanks to @djc for contributing to this release! [#1917]: #1917 [#1911]: #1911 Closes #1919
hawkw
added a commit
that referenced
this pull request
Feb 11, 2022
# 0.17.1 (February 11, 2022) ### Added - `OpenTelemetryLayer` can now add detailed location information to forwarded events (defaults to on) ([#1911]) - `OpenTelemetryLayer::with_event_location` to control whether source locations are recorded ([#1911]) ### Changed - Avoid unnecessary allocations to improve performance when recording events ([#1917]) Thanks to @djc for contributing to this release! [#1917]: #1917 [#1911]: #1911 Closes #1919
|
This was done in #1922. |
kaffarell
pushed a commit
to kaffarell/tracing
that referenced
this pull request
May 22, 2024
# 0.17.1 (February 11, 2022) ### Added - `OpenTelemetryLayer` can now add detailed location information to forwarded events (defaults to on) ([tokio-rs#1911]) - `OpenTelemetryLayer::with_event_location` to control whether source locations are recorded ([tokio-rs#1911]) ### Changed - Avoid unnecessary allocations to improve performance when recording events ([tokio-rs#1917]) Thanks to @djc for contributing to this release! [tokio-rs#1917]: tokio-rs#1917 [tokio-rs#1911]: tokio-rs#1911 Closes tokio-rs#1919
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.
As discussed in #1911, prepares a point release for tracing-opentelemetry. This follows the changes made in #1877 for the 0.16.0 release.
(I'm confused by the backport/release strategy in this repo -- #1877 targeted the master branch, but a commit with a subset of those changes ended up in the 0.1.x branch, and the crates.io version was apparently published from v0.1.x. Definitely feels to me like life would be better if v0.1.x was the default branch for this repo -- I'm pretty sure merging forward is easier than merging backward, too.)