build(deps): bump uuid from 1.23.4 to 1.24.1 in /apps/desktop/src-tauri

[dependabot]

Bumps uuid from 1.23.4 to 1.24.1.

Release notes

Sourced from uuid's releases.

v1.24.1

What's Changed

• Fix non-ASCII character handling in parse diagnostics by @​questfever in uuid-rs/uuid#899
• Prepare for 1.24.1 release by @​KodrAus in uuid-rs/uuid#900

New Contributors

• @​questfever made their first contribution in uuid-rs/uuid#899

Full Changelog: uuid-rs/uuid@v1.24.0...v1.24.1

v1.24.0

What's Changed

• feat(fmt): support encoding into MaybeUninit buffers by @​weifanglab in uuid-rs/uuid#892
• Prepare for 1.24.0 release by @​KodrAus in uuid-rs/uuid#896

New Contributors

• @​weifanglab made their first contribution in uuid-rs/uuid#892

Full Changelog: uuid-rs/uuid@v1.23.5...v1.24.0

v1.23.5

What's Changed

• doc: Fix broken link by @​frostyplanet in uuid-rs/uuid#891
• perf: Optimize UUID hex parsing and formatting by @​geeknoid in uuid-rs/uuid#894
• Prepare for 1.23.5 release by @​KodrAus in uuid-rs/uuid#895

New Contributors

• @​geeknoid made their first contribution in uuid-rs/uuid#894

Full Changelog: uuid-rs/uuid@v1.23.4...v1.23.5

Commits

• 2ea38af Merge pull request #900 from uuid-rs/cargo/v1.24.1
• 9dbeb04 prepare for 1.24.1 release
• e113df8 Merge pull request #899 from questfever/main
• b017765 Fix non-ASCII character handling in parse diagnostics
• 6a8aeab Merge pull request #896 from uuid-rs/cargo/v1.24.0
• e6db8ec prepare for 1.24.0 release
• 606f236 Merge pull request #892 from weifanglab/main
• ab848db feat(fmt): support encoding into MaybeUninit buffers
• 5dc6b3d Merge pull request #895 from uuid-rs/cargo/v1.23.5
• 5a7dfe5 prepare for 1.23.5 release
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b.

• Head SHA: 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b

• Workflow run: 32172922200

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: Cargo.lock"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: Cargo.lock"]
  R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b
• Workflow run: 32180502937
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b.

• Head SHA: 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b

• Workflow run: 32180502937

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: Cargo.lock"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: Cargo.lock"]
  R1 --> V1["required checks"]

Loading

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b.

• Head SHA: 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b

• Workflow run: 32180502937

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: Cargo.lock"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: Cargo.lock"]
  R1 --> V1["required checks"]

Loading

[seonghobae]

Reviewed exact head 77a2c35a21eeaf6273ea6bf825d9ea0c1793f33b against protected develop@acdbea6344fe1231c39535b575f4de35e4c607c9. The diff is exactly the Cargo.lock uuid 1.23.4→1.24.1 package/checksum update. Exact-head ci, cross-platform build-baseline, release, sbom, Bandit, SAST Semgrep, and secret-scan are terminal-success; dependency-review, Scorecard, and base-vs-head OSV comparison also succeed with no PR-introduced vulnerability. The standalone security-audit stops at the inherited protected-base npm findings before its Rust step, while the aggregate Trivy/OSV scanners do inspect Cargo and report no uuid finding; the aggregate failure remains the protected-base PDF.js lane owned by #783. No inline review threads are open. APPROVE is code-review evidence only; merge still requires fresh terminal-success of the inherited security and central coverage/OpenCode gates.

[dependabot]

Superseded by #1027.