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.

Sign up for GitHub

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

Jump to bottom

changelog: clarify implications of env-filter not being enabled #1700

Merged
merged 1 commit into from Nov 3, 2021
Merged

changelog: clarify implications of env-filter not being enabled #1700

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion tracing-subscriber/CHANGELOG.md
View file
Open in desktop
Expand Up @@ -32,7 +32,8 @@ deprecated APIs, and more.
- Replaced the [`chrono` crate] with the [`time` crate] for timestamp formatting, to
resolve [RUSTSEC-2020-0159] ([#1646])
- Removed `json` and `env-filter` from default features. They must now be
enabled explictly ([#1647])
enabled explictly ([#1647]). This means that `RUST_LOG`-based filters _will not_
work unless the `env-filter` feature is enabled.
- Changed `FormatEvent::format_event` and `FormatFields::format_fields`
trait methods to take a `Writer` type, rather than a `&mut dyn fmt::Write`
trait object ([#1661])
Expand Down