Update Rust crate env_logger to 0.11.8

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
env_logger	dependencies	minor	0.10.2 -> 0.11.8

---

Release Notes

rust-cli/env_logger (env_logger)

v0.11.8

Compare Source

Compatibility

• (kv) Deprecate the unstable-kv feature which may be removed in a future patch release

Features

• (kv) Stabilize key-value support behind the kv feature
• Expose ConfigurableFormat to build custom [Builder::format]s that leverage this

v0.11.7

Compare Source

Internal

• Replaced humantime with jiff

v0.11.6

Compare Source

Features

• Opt-in file and line rendering

v0.11.5

Compare Source

v0.11.4

Compare Source

v0.11.3

Compare Source

Features

• Experimental support for key-value logging behind unstable-kv

v0.11.2

Compare Source

v0.11.1

Compare Source

Fixes

• Allow styling with Target::Pipe

v0.11.0

Compare Source

Migration Guide

env_logger::fmt::Style:
The bespoke styling API, behind color, was removed, in favor of accepting any
ANSI styled string and adapting it to the target stream's capabilities.

Possible styling libraries include:

• anstyle is a minimal, runtime string styling API and is re-exported as env_logger::fmt::style
• owo-colors is a feature rich runtime string styling API
• color-print for feature-rich compile-time styling API

custom_format.rs
uses anstyle via
Formatter::default_level_style

Breaking Change

• Removed bespoke styling API
  • env_logger::fmt::Formatter::style
  • env_logger::fmt::Formatter::default_styled_level
  • env_logger::fmt::Style
  • env_logger::fmt::Color
  • env_logger::fmt::StyledValue
• Removed env_logger::filter in favor of env_filter

Compatibility

MSRV changed to 1.71

Features

• Automatically adapt ANSI escape codes in logged messages to the current terminal's capabilities
• Add support for NO_COLOR and CLICOLOR_FORCE, see https://bixense.com/clicolors/

Fixes

• Print colors when is_test(true)

---

Configuration

📅 Schedule: Branch creation - "after 8pm,before 6am" in timezone America/Los_Angeles, Automerge - "after 8pm,before 6am" in timezone America/Los_Angeles.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.11.8
    Updating crates.io index
error: failed to select a version for the requirement `env_logger = "^0.10"`
candidate versions found which didn't match: 0.11.8
location searched: crates.io index
required by package `lpc55_sign v0.3.4 (https://github.com/oxidecomputer/lpc55_support#131520fc)`
    ... which satisfies git dependency `lpc55_sign` (locked to 0.3.4) of package `oks v0.3.3 (/tmp/renovate/repos/github/oxidecomputer/offline-keystore)`

[flihp]

lpc55-support is holding this back as the lpc55-sign tool is currently locked to the 0.10 release. 0.11 removed the API for doing colors. They've published a migration guide but upgrading lpc55-sign looks like a non-trivial amount of work.