From 6eeef56b5102aa7e133864810c75363087b4c1eb Mon Sep 17 00:00:00 2001 From: David Barsky Date: Wed, 3 Nov 2021 13:52:54 -0400 Subject: [PATCH] changelog: Clarify implications of `env-filter` not being the default (#1700) Resolves #1697 by documenting this change in the CHANGELOG.md. --- tracing-subscriber/CHANGELOG.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tracing-subscriber/CHANGELOG.md b/tracing-subscriber/CHANGELOG.md index c72d7d3d5..89df1fa0a 100644 --- a/tracing-subscriber/CHANGELOG.md +++ b/tracing-subscriber/CHANGELOG.md @@ -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])