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

Update tracing-subscriber requirement from 0.2.16 to 0.3.15 #25

Closed

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jul 21, 2022

Updates the requirements on tracing-subscriber to permit the latest version.

Release notes

Sourced from tracing-subscriber's releases.

tracing-subscriber 0.3.15

This release fixes a bug where the reload layer would fail to pass through max_level_hint to the underlying layer, potentially breaking filtering.

Fixed

  • reload: pass through max_level_hint to the inner Layer (#2204)

Thanks to @​guswynn for contributing to this release!

#2204: tokio-rs/tracing#2204

Commits
  • 290eff2 subscriber: prepare to release v0.3.15 (#2237)
  • 398a6ec core: implement PartialEq, Eq for Metadata, FieldSet (#2229)
  • 28a0c99 appender: add a builder for constructing RollingFileAppenders (#2227)
  • 463b699 core: remove misleading dispatcher docs (#2220)
  • 8fbdb1c tracing: allow owned values and fat pointers in Span::record (#2212)
  • 21cdf08 appender: name spawned thread (#2219)
  • 7533872 docs: remove hard coded version link from readme (#2208)
  • 65093b3 chore(ci): update actions/checkout action to v3 (#2213)
  • d7139a5 subscriber: pass through max_level_hint in reload (#2204)
  • 9c4bd43 attributes: prepare to release v0.1.22 (#2203)
  • Additional commits viewable in compare view

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)

Updates the requirements on [tracing-subscriber](https://github.com/tokio-rs/tracing) to permit the latest version.
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.2.16...tracing-subscriber-0.3.15)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 21, 2022
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Oct 7, 2022

Superseded by #27.

@dependabot dependabot bot closed this Oct 7, 2022
@dependabot dependabot bot deleted the dependabot/cargo/tracing-subscriber-0.3.15 branch October 7, 2022 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants