Closed renovate[bot] closed 1 week ago
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
tap-agent/src/agent/sender_account.rs | 4 | 79.97% | ||
<!-- | Total: | 4 | --> |
Totals | |
---|---|
Change from base Build 9653668456: | -0.07% |
Covered Lines: | 3870 |
Relevant Lines: | 5791 |
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
tap-agent/src/agent/sender_account.rs | 4 | 79.97% | ||
<!-- | Total: | 4 | --> |
Totals | |
---|---|
Change from base Build 9653668456: | -0.07% |
Covered Lines: | 3870 |
Relevant Lines: | 5791 |
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
tap-agent/src/agent/sender_account.rs | 4 | 79.97% | ||
<!-- | Total: | 4 | --> |
Totals | |
---|---|
Change from base Build 9653668456: | -0.07% |
Covered Lines: | 3870 |
Relevant Lines: | 5791 |
@LNSD it seems that renovate doesn't know about the "tradition" of
v0.x.x
versions making breaking changes while only bumping the feature version. Perhaps is there a way to make renovate aware of that?
It is using cargo update
underneath, so I believe it is aware of the Rust semantic versioning. What are your concerns?
Totals | |
---|---|
Change from base Build 9666456727: | 0.0% |
Covered Lines: | 3874 |
Relevant Lines: | 5791 |
Totals | |
---|---|
Change from base Build 9666456727: | 0.0% |
Covered Lines: | 3874 |
Relevant Lines: | 5791 |
Totals | |
---|---|
Change from base Build 9666456727: | 0.0% |
Covered Lines: | 3874 |
Relevant Lines: | 5791 |
@LNSD it seems that renovate doesn't know about the "tradition" of
v0.x.x
versions making breaking changes while only bumping the feature version. Perhaps is there a way to make renovate aware of that?It is using
cargo update
underneath, so I believe it is aware of the Rust semantic versioning. What are your concerns?
This could be a breaking change
@LNSD it seems that renovate doesn't know about the "tradition" of
v0.x.x
versions making breaking changes while only bumping the feature version. Perhaps is there a way to make renovate aware of that?It is using
cargo update
underneath, so I believe it is aware of the Rust semantic versioning. What are your concerns?This could be a breaking change
I understand. But, if we have the right CI checks, we can catch these issues.
In any case, I don't see any issue with this specific dependency upgrade. I would approve this PR and merge it
This PR contains the following updates:
0.9.0
->0.11.0
Release Notes
rust-cli/env_logger (env_logger)
### [`v0.11.3`](https://togithub.com/rust-cli/env_logger/blob/HEAD/CHANGELOG.md#0113---2024-03-05) [Compare Source](https://togithub.com/rust-cli/env_logger/compare/v0.11.2...v0.11.3) ##### Features - Experimental support for key-value logging behind `unstable-kv` ### [`v0.11.2`](https://togithub.com/rust-cli/env_logger/blob/HEAD/CHANGELOG.md#0112---2024-02-13) [Compare Source](https://togithub.com/rust-cli/env_logger/compare/v0.11.1...v0.11.2) ### [`v0.11.1`](https://togithub.com/rust-cli/env_logger/blob/HEAD/CHANGELOG.md#0111---2024-01-27) [Compare Source](https://togithub.com/rust-cli/env_logger/compare/v0.11.0...v0.11.1) ##### Fixes - Allow styling with `Target::Pipe` ### [`v0.11.0`](https://togithub.com/rust-cli/env_logger/blob/HEAD/CHANGELOG.md#0110---2024-01-19) [Compare Source](https://togithub.com/rust-cli/env_logger/compare/v0.10.2...v0.11.0) ##### 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](https://docs.rs/anstyle) is a minimal, runtime string styling API and is re-exported as `env_logger::fmt::style` - [owo-colors](https://docs.rs/owo-colors) is a feature rich runtime string styling API - [color-print](https://docs.rs/color-print) for feature-rich compile-time styling API [custom_format.rs](https://docs.rs/env_logger/latest/src/custom_format/custom_format.rs.html) uses `anstyle` via [`Formatter::default_level_style`](https://docs.rs/env_logger/latest/env_logger/fmt/struct.Formatter.html#method.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)` ### [`v0.10.2`](https://togithub.com/rust-cli/env_logger/blob/HEAD/CHANGELOG.md#0102---2024-01-18) [Compare Source](https://togithub.com/rust-cli/env_logger/compare/v0.10.1...v0.10.2) ##### Performance - Avoid extra UTF-8 validation performed in some cases ##### Fixes - Ensure custom pipes/stdout get flushed - Don't panic on broken pipes when `color` is disabled ### [`v0.10.1`](https://togithub.com/rust-cli/env_logger/blob/HEAD/CHANGELOG.md#0101---2023-11-10) [Compare Source](https://togithub.com/rust-cli/env_logger/compare/v0.10.0...v0.10.1) ##### Performance - Avoid hashing directives and accessing RNG on startup ##### Documentation - Tweak `RUST_LOG` documentation ### [`v0.10.0`](https://togithub.com/rust-cli/env_logger/blob/HEAD/CHANGELOG.md#0100---2022-11-24) [Compare Source](https://togithub.com/rust-cli/env_logger/compare/v0.9.3...v0.10.0) MSRV changed to 1.60 to hide optional dependencies ##### Fixes - Resolved soundness issue by switching from `atty` to `is-terminal` ##### Breaking Changes To open room for changing dependencies: - Renamed `termcolor` feature to `color` - Renamed `atty` feature to `auto-color`Configuration
📅 Schedule: Branch creation - "before 6am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 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.
This PR has been generated by Mend Renovate. View repository job log here.