tracing: prepare to release v0.1.23 #1223
Merged
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.
Fixed
#[instrument(err)]onfunctions with mutable parameters ([attributes: fix #[instrument(err)] with mutable parameters #1167])
#[instrument]withasync-trait([attributes: add visibility to async-trait output #977])synfeatures ([attributes: remove unnecessary syn features #928])tracingmacros would generate codefor events whose levels are disabled statically by the
logcrate'sstatic_max_level_XXXfeatures ([tracing: checklogmax level prior to dispatch check #1175])deny(broken_intra_doc_links)#981],[docs: add tracing-elastic-apm to related crates #1146], [attributes: update & improve docs #1215])
Changed
tracing-futuresdependency is no longer requiredwhen using
#[instrument]on async functions ([tracing: Instrument std::future::Future in tracing #808])tracing-attributesminimum dependency tov0.1.12 ([tracing: update minimum
tracing-attributesto 0.1.12 #1222])Thanks to @nagisa, @Txuritan, @TaKO8Ki, @okready, and @krojew for
contributing to this release!