deps(deps): bump env_logger from 0.10.2 to 0.11.11

[dependabot]

Bumps env_logger from 0.10.2 to 0.11.11.

Release notes

Sourced from env_logger's releases.

v0.11.11

[0.11.11] - 2026-06-25

Internal

• Updated env_filter

v0.11.10

[0.11.10] - 2026-03-23

Internal

• Update dependencies

v0.11.9

[0.11.9] - 2026-02-11

v0.11.8

[0.11.8] - 2025-04-01

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

[0.11.7] - 2025-03-10

Internal

• Replaced humantime with jiff

v0.11.6

[0.11.6] - 2024-12-20

Features

• Opt-in file and line rendering

v0.11.5

[0.11.5] - 2024-07-25

v0.11.4

[0.11.4] - 2024-07-23

v0.11.3

... (truncated)

Changelog

Sourced from env_logger's changelog.

[0.11.11] - 2026-06-25

Internal

• Updated env_filter

[0.11.10] - 2026-03-23

Internal

• Update dependencies

[0.11.9] - 2026-02-11

[0.11.8] - 2025-04-01

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

[0.11.7] - 2025-03-10

Internal

• Replaced humantime with jiff

[0.11.6] - 2024-12-20

Features

• Opt-in file and line rendering

[0.11.5] - 2024-07-25

[0.11.4] - 2024-07-23

[0.11.3] - 2024-03-05

Features

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

[0.11.2] - 2024-02-13

[0.11.1] - 2024-01-27

... (truncated)

Commits

• b4d3f2b chore: Release
• cc2b2ef chore: Release
• 69e27d1 docs: Update changelog
• 166880d Merge pull request #411 from epage/parse
• 0a580d0 fix(filter): Remove 'parse' on no_std
• 78d8ef1 Merge pull request #404 from cagatay-y/feature/filter-no_std
• 132fe86 feat(filter): Add support for no_std environments
• 4feafa4 refactor(env_filter): Fix unreachable pub warning
• 92f8d8d Merge pull request #410 from rust-cli/renovate/crate-ci-typos-1.x
• 4e57784 chore(deps): Update pre-commit hook crate-ci/typos to v1.47.0
• Additional commits viewable in compare view

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 4c08557a-0f04-4335-a700-d186e8394971

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[proggeramlug]

Holding this out of the merge trains for one reason, and it is worth stating precisely because three other PRs share it.

benchmarks/public_baseline.py fingerprints the root Cargo.toml as a SOURCE_PATHS input, and _fingerprint_bytes hashes the whole file after normalizing only the workspace version. So a dependency line change invalidates the published benchmark artifact and hard-fails the required step:

lint :: Public benchmark evidence freshness
public artifact benchmark inputs changed; regenerate it with ./benchmarks/run_public_baseline.sh

This is not the three-week-old known-red that most open PRs were carrying — that one is fixed; main is green on this step since 2f854511e9, and train 258's CI was 22/22.

I checked which of the five open cargo bumps actually trip it, by diffing each one's root Cargo.toml against main excluding the version line:

• deps(deps): bump base64 from 0.22.1 to 0.23.1 #11062 (base64 = "0.22" → "0.23") — trips it
• deps(deps): bump env_logger from 0.10.2 to 0.11.11 #11063 (env_logger = "0.10" → "0.11") — trips it
• deps(deps): bump ed25519-dalek from 2.2.0 to 3.0.0 #11064, deps(deps): bump tungstenite from 0.24.0 to 0.30.0 #11065, deps(deps): bump the cargo-minor-and-patch group across 1 directory with 8 updates #11067 — do not: their manifest edits are in crate-level Cargo.tomls and Cargo.lock, neither of which is fingerprinted. Those three can land normally and I am taking them in the next train.

Regenerating the artifact is ./benchmarks/run_public_baseline.sh — roughly two hours, pinned to Node v22.23.1 and Bun 1.3.14, and it additionally requires a quiet host (CPU ≤ 25% for 60 consecutive seconds). The pin and the measurement are atomic by design.

So the plan for this PR: batch it with #11063 and #11083 (turnloop → alpha.8, same blocker) and pay for one regeneration covering all three, rather than three. I'll pick that up as a dedicated PR. Nothing is wrong with the bump itself.

[proggeramlug]

Landed on main in merge train 270 (#11132, v0.5.1653). The train rebase gives commits new SHAs, so GitHub cannot close this automatically.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.