chore(deps): bump sha2 from 0.10.9 to 0.11.0 in /src-tauri

[dependabot]

Bumps sha2 from 0.10.9 to 0.11.0.

Commits

• ffe0939 Release sha2 0.11.0 (#806)
• 8991b65 Use the standard order of the [package] section fields (#807)
• 3d2bc57 sha2: refactor backends (#802)
• faa55fb sha3: bump keccak to v0.2 (#803)
• d3e6489 sha3 v0.11.0-rc.9 (#801)
• bbf6f51 sha2: tweak backend docs (#800)
• 155dbbf sha3: add default value for the DS generic parameter on TurboShake128/256...
• ed514f2 Use published version of keccak v0.2 (#799)
• 702bcd8 Migrate to closure-based keccak (#796)
• 827c043 sha3 v0.11.0-rc.8 (#794)
• 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)

[greptile-apps]

Greptile Summary

This is a Dependabot-generated bump of sha2 from 0.10.9 to 0.11.0 in the Tauri backend. The project's only usage of sha2 is in the verify_sha256 function, which calls Sha256::new(), .update(), and .finalize() — all of which are stable across the version boundary.

• The lock file correctly retains sha2 0.10.9 for indirect dependents (tauri-build, tao) that have not yet migrated to the 0.11 ecosystem; this is normal Cargo behavior for semver-incompatible crates.
• sha2 0.11.0 introduces a new dependency subtree (digest 0.11, block-buffer 0.12, hybrid-array, const-oid, cpufeatures 0.3) and bumps MSRV to Rust 1.85; projects building with an older toolchain without a pinned rust-toolchain.toml should verify their CI Rust version is ≥ 1.85.

Confidence Score: 5/5

Safe to merge — the only sha2 call site uses the stable Sha256::new() / .update() / .finalize() API that is unchanged across this version boundary.

The project's sole usage of sha2 is chunked file hashing with basic Digest trait methods, fully compatible with 0.11's API. Both old and new sha2 versions coexist cleanly in the lock file for packages still on 0.10.9. The one thing worth watching is the MSRV bump to Rust 1.85 introduced by sha2 0.11, since no rust-toolchain.toml is present to pin the toolchain.

No files require special attention. The absence of a rust-toolchain.toml means CI must be running Rust >= 1.85 to build successfully.

Important Files Changed

Filename	Overview
src-tauri/Cargo.toml	Single-line version bump of sha2 from "0.10" to "0.11"; no other dependencies changed.
src-tauri/Cargo.lock	Adds sha2 0.11.0 and its new dependency subtree (digest 0.11.3, block-buffer 0.12.0, hybrid-array 0.4.12, crypto-common 0.2.1, cpufeatures 0.3.0, const-oid 0.10.2); retains sha2 0.10.9 for indirect dependents that haven't migrated.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    openloop["openloop binary"]
    tauri_build["tauri-build (indirect)"]
    tao["tao (indirect)"]
    sha2_new["sha2 0.11.0"]
    sha2_old["sha2 0.10.9"]
    digest_new["digest 0.11.3"]
    digest_old["digest 0.10.7"]
    bb_new["block-buffer 0.12.0"]
    bb_old["block-buffer 0.10.4"]
    cc_new["crypto-common 0.2.1"]
    cc_old["crypto-common 0.1.7"]
    cpu_new["cpufeatures 0.3.0"]
    cpu_old["cpufeatures 0.2.17"]
    hybrid["hybrid-array 0.4.12"]
    const_oid["const-oid 0.10.2"]
    openloop -->|"bumped to"| sha2_new
    tauri_build --> sha2_old
    tao --> sha2_old
    sha2_new --> digest_new
    sha2_new --> cpu_new
    sha2_old --> digest_old
    sha2_old --> cpu_old
    digest_new --> bb_new
    digest_new --> cc_new
    digest_new --> const_oid
    digest_old --> bb_old
    digest_old --> cc_old
    bb_new --> hybrid
    cc_new --> hybrid

Loading

_{Reviews (1): Last reviewed commit: "chore(deps): bump sha2 from 0.10.9 to 0...." | Re-trigger Greptile}

[dependabot]

Looks like sha2 is up-to-date now, so this is no longer needed.