renovate[bot]
commented
10 months ago ⚠ 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: rust/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path rust/optics-base/Cargo.toml --package tracing-error@0.1.2 --precise 0.2.0
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
Updating crates.io index
error: failed to select a version for the requirement `tracing-error = "^0.1.2"`
candidate versions found which didn't match: 0.2.0
location searched: crates.io index
required by package `color-eyre v0.5.11`
... which satisfies dependency `color-eyre = "^0.5.0"` (locked to 0.5.11) of package `optics-core v0.1.0 (/tmp/renovate/repos/github/celo-org/optics-monorepo/rust/optics-core)`
perhaps a crate was updated and forgotten to be re-vendored?
This PR contains the following updates:
0.1.2->0.2.0Release Notes
tokio-rs/tracing (tracing-error)
### [`v0.2.0`](https://togithub.com/tokio-rs/tracing/releases/tag/tracing-log-0.2.0): tracing-log 0.2.0 [Compare Source](https://togithub.com/tokio-rs/tracing/compare/tracing-error-0.1.2...tracing-error-0.2.0) This release contains two breaking changes: the removal of the `env_logger` and `trace_logger` features. Below are the suggested migration paths: - `env_logger`: users should use [`tracing_subscriber::fmt::Subscriber`][tracing_subscriber::fmt::Subscriber] or [`tracing_subscriber::fmt::Layer`][tracing_subscriber::fmt::Layer] with the [`Targets`][Targets] or [`EnvFilter`][EnvFilter] filters instead. - `trace_logger`: users should use the `tracing` crate's ["log" feature flag][log-feature] instead. ##### Breaking Changes - Remove deprecated `env_logger` feature. This removes the dependency on the unmaintained `atty` crate, resolving the security advisory [GHSA-g98v-hv3f-hcfr]/[RUSTSEC-2021-0145]. ([#2771]) - Remove deprecated `trace_logger` feature. ([#2771]) [#2771]: https://togithub.com/tokio-rs/tracing/pull/2771 [`tracing_subscriber::fmt::Subscriber`]: https://docs.rs/tracing-subscriber/0.3.17/tracing_subscriber/fmt/struct.Subscriber.html [`tracing_subscriber::fmt::Layer`]: https://docs.rs/tracing-subscriber/0.3.17/tracing_subscriber/fmt/struct.Layer.html [`Targets`]: https://docs.rs/tracing-subscriber/0.3.17/tracing_subscriber/filter/targets/struct.Targets.html [`EnvFilter`]: https://docs.rs/tracing-subscriber/0.3.17/tracing_subscriber/filter/struct.EnvFilter.html [log-feature]: https://docs.rs/tracing/latest/tracing/#emitting-log-records [GHSA-g98v-hv3f-hcfr]: https://togithub.com/advisories/GHSA-g98v-hv3f-hcfr [RUSTSEC-2021-0145]: https://rustsec.org/advisories/RUSTSEC-2021-0145.htmlConfiguration
📅 Schedule: Branch creation - "before 4am 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.