fix(build): the lockfile edge that made every cargo job fail

`main` has been red since 3eeda05. `Cargo.lock` carried a dependency edge to
`thiserror 2.0.19` while its own package entry said `2.0.20` — a lockfile Cargo
wants to repair and `--locked` forbids repairing, so every cargo job in every
workflow died before compiling a crate:

    error: cannot update the lock file ... because --locked was passed to prevent this

The Dependabot bump (b4ab2d9) moved the package entry; 2abfef6 touched the file
afterwards and the stale edge survived. CI had gone green on a base predating
the bump, which is the same shape as the ruff-pin defect recorded in P4.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Opus 5 committed 2026-08-14 17:32:20 +07:00
1 parent 3eeda059c8
commit 2f81b0c6ca
8 files changed
+1 -1

No files matched your search

Generated
+1 -1
View File
@@ -4703,7 +4703,7 @@ dependencies = [
"serde",
"serde_json",
"tauri",
"thiserror 2.0.19",
"thiserror 2.0.20",
"tokio",
"tracing",
"windows-sys 0.60.2",
Binary file not shown.

After

Width:  |  Height:  |  Size: 71 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 110 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 104 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 60 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 52 KiB