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

Bump tracing-subscriber from 0.3.15 to 0.3.16 #178

Merged
merged 1 commit into from
Oct 8, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 7, 2022

Bumps tracing-subscriber from 0.3.15 to 0.3.16.

Release notes

Sourced from tracing-subscriber's releases.

tracing-subscriber 0.3.16

This release of tracing-subscriber fixes a regression introduced in [v0.3.15][subscriber-0.3.15] where Option::None's Layer implementation would set the max level hint to OFF. In addition, it adds several new APIs, including the Filter::event_enabled method for filtering events based on fields values, and the ability to log internal errors that occur when writing a log line.

This release also replaces the dependency on the unmaintained [ansi-term] crate with the [nu-ansi-term] crate, resolving an informational security advisory ([RUSTSEC-2021-0139]) for [ansi-term]'s maintainance status. This increases the minimum supported Rust version (MSRV) to Rust 1.50+, although the crate should still compile for the previous MSRV of Rust 1.49+ when the ansi feature is not enabled.

Fixed

  • layer: Option::None's Layer impl always setting the max_level_hint to LevelFilter::OFF (#2321)
  • Compilation with -Z minimal versions (#2246)
  • env-filter: Clarify that disabled level warnings are emitted by tracing-subscriber (#2285)

Added

  • fmt: Log internal errors to stderr if writing a log line fails (#2102)
  • fmt: FmtLayer::log_internal_errors and FmtSubscriber::log_internal_errors methods for configuring whether internal writer errors are printed to stderr (#2102)
  • fmt: #[must_use] attributes on builders to warn if a Subscriber is configured but not set as the default subscriber (#2239)
  • filter: Filter::event_enabled method for filtering an event based on its fields (#2245, #2251)
  • filter: Targets::default_level accessor (#2242)

Changed

  • ansi: Replaced dependency on unmaintained ansi-term crate with nu-ansi-term ((#2287, fixes informational advisory [RUSTSEC-2021-0139])
  • tracing-core: updated to [0.1.30][core-0.1.30]
  • Minimum Supported Rust Version (MSRV) increased to Rust 1.50+ (when the ansi) feature flag is enabled (#2287)

Documented

  • fmt: Correct inaccuracies in fmt::init documentation (#2224)
  • filter: Fix incorrect doc link in filter::Not combinator (#2249)

Thanks to new contributors @​cgbur, @​DesmondWillowbrook, @​RalfJung, and @​poliorcetics, as well as returning contributors @​CAD97, @​connec, @​jswrenn,

... (truncated)

Commits
  • b28c935 subscriber: prepare to release v0.3.16 (#2342)
  • ecd7e06 chore(ci): remove requirement for removed job
  • a42e963 subscriber: replace unmaintained ansi_term with nu-ansi-term (#2287)
  • a4fc92c subscriber: revert "impl LookupSpan for Box\<LS> and Arc\<LS> (#2247)"
  • 8e35927 tracing: prepare to release v0.1.37 (#2341)
  • 64b221d attributes: prepare to release v0.1.23 (#2340)
  • 92cb2f0 attributes: fix handling of inner attributes (#2307)
  • 8b01ea9 core: prepare to release v0.1.30 (#2339)
  • d7372d7 tracing: add reqwest-tracing to related crates in README (#2331)
  • 257f86f opentelemetry: fix metrics docs using value. instead of histogram. (#2326)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added Bot Bot Dep Dependency labels Oct 7, 2022
@AurevoirXavier AurevoirXavier enabled auto-merge (squash) October 7, 2022 17:25
Bumps [tracing-subscriber](https://github.com/tokio-rs/tracing) from 0.3.15 to 0.3.16.
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.15...tracing-subscriber-0.3.16)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/cargo/tracing-subscriber-0.3.16 branch from 4e8371f to 6c2254f Compare October 7, 2022 17:26
@AurevoirXavier AurevoirXavier merged commit 03e3999 into main Oct 8, 2022
@AurevoirXavier AurevoirXavier deleted the dependabot/cargo/tracing-subscriber-0.3.16 branch October 8, 2022 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Bot Dep Dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant