Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core: prepare to release v0.1.22 #1897

Merged
merged 2 commits into from
Feb 4, 2022
Merged

core: prepare to release v0.1.22 #1897

merged 2 commits into from
Feb 4, 2022

Conversation

hawkw
Copy link
Member

@hawkw hawkw commented Feb 4, 2022

0.1.22 (February 3, 2022)

This release adds experimental support for recording structured field
values using the valuable crate. See this blog post for
details on valuable.

Note that valuable support currently requires --cfg tracing_unstable. See the documentation for details.

Added

  • field: Experimental support for recording field values using the
    valuable crate (#1608, #1888, #1887)
  • field: Added ValueSet::record method (#1823)
  • subscriber: Default impl for NoSubscriber (#1785)
  • metadata: New Kind::HINT to support the enabled! macro in
    tracing (#1883, #1891)

Fixed

Thanks to @xd009642, @Skepfyr, @guswynn, @Folyd, and @mbergkvist for
contributing to this release!

# 0.1.22 (February 3, 2022)

This release adds *experimental* support for recording structured field
values using the [`valuable`] crate. See [this blog post][post] for
details on `valuable`.

Note that `valuable` support currently requires `--cfg
tracing_unstable`. See the documentation for details.

### Added

- **field**: Experimental support for recording field values using the
  [`valuable`] crate ([#1608], [#1888], [#1887])
- **field**: Added `ValueSet::record` method ([#1823])
- **subscriber**: `Default` impl for `NoSubscriber` ([#1785])
- **metadata**: New `Kind::HINT` to support the `enabled!` macro in
  `tracing` ([#1883], [#1891])
### Fixed

- Fixed a number of documentation issues ([#1665], [#1692], [#1737])

Thanks to @xd009642, @Skepfyr, @guswynn, @Folyd, and @mbergkvist for
contributing to this release!
@hawkw hawkw self-assigned this Feb 4, 2022
@hawkw hawkw requested a review from a team as a code owner February 4, 2022 00:25
@hawkw hawkw enabled auto-merge (squash) February 4, 2022 00:26
@hawkw hawkw disabled auto-merge February 4, 2022 00:26
@hawkw hawkw enabled auto-merge (squash) February 4, 2022 00:26
@hawkw hawkw merged commit 0f8326b into v0.1.x Feb 4, 2022
@hawkw hawkw deleted the eliza/tracing-core-0.1.22 branch February 4, 2022 00:52
kaffarell pushed a commit to kaffarell/tracing that referenced this pull request May 22, 2024
# 0.1.22 (February 3, 2022)

This release adds *experimental* support for recording structured field
values using the [`valuable`] crate. See [this blog post][post] for
details on `valuable`.

Note that `valuable` support currently requires `--cfg
tracing_unstable`. See the documentation for details.

### Added

- **field**: Experimental support for recording field values using the
  [`valuable`] crate ([tokio-rs#1608], [tokio-rs#1888], [tokio-rs#1887])
- **field**: Added `ValueSet::record` method ([tokio-rs#1823])
- **subscriber**: `Default` impl for `NoSubscriber` ([tokio-rs#1785])
- **metadata**: New `Kind::HINT` to support the `enabled!` macro in
  `tracing` ([tokio-rs#1883], [tokio-rs#1891])
### Fixed

- Fixed a number of documentation issues ([tokio-rs#1665], [tokio-rs#1692], [tokio-rs#1737])

Thanks to @xd009642, @Skepfyr, @guswynn, @Folyd, and @mbergkvist for
contributing to this release!

[`valuable`]: https://crates.io/crates/valuable
[post]: https://tokio.rs/blog/2021-05-valuable
[tokio-rs#1608]: tokio-rs#1608
[tokio-rs#1888]: tokio-rs#1888
[tokio-rs#1887]: tokio-rs#1887
[tokio-rs#1823]: tokio-rs#1823
[tokio-rs#1785]: tokio-rs#1785
[tokio-rs#1883]: tokio-rs#1883
[tokio-rs#1891]: tokio-rs#1891
[tokio-rs#1665]: tokio-rs#1665
[tokio-rs#1692]: tokio-rs#1692
[tokio-rs#1737]: tokio-rs#1737
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants