SakulFlee / Akimo-Project

Other
0 stars 0 forks source link

Update Rust crate log to v0.4.22 #181

Open renovate[bot] opened 3 weeks ago

renovate[bot] commented 3 weeks ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
log dependencies patch 0.4.20 -> 0.4.22
log dependencies patch 0.4.21 -> 0.4.22

Release Notes

rust-lang/log (log) ### [`v0.4.22`](https://togithub.com/rust-lang/log/blob/HEAD/CHANGELOG.md#0422---2024-06-27) [Compare Source](https://togithub.com/rust-lang/log/compare/0.4.21...0.4.22) ### [`v0.4.21`](https://togithub.com/rust-lang/log/blob/HEAD/CHANGELOG.md#0421---2024-02-27) [Compare Source](https://togithub.com/rust-lang/log/compare/0.4.20...0.4.21)

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about these updates again.



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 3 weeks 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:

The artifact failure details are included below:

File name: WGPU-Engine/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path WGPU-Engine/Cargo.toml --workspace
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/SakulFlee/Akimo-Project/WGPU-Engine/Cargo.toml
workspace: /tmp/renovate/repos/github/SakulFlee/Akimo-Project/Cargo.toml

this may be fixable by adding `WGPU-Engine` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/SakulFlee/Akimo-Project/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.