chore(deps): bump blake3 in /czech-file-knife

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps blake3 in /czech-file-knife from 1.8.5 to 1.8.7.

Updates blake3 from 1.8.5 to 1.8.7

Release notes

Sourced from blake3's releases.

1.8.7

version 1.8.7

Changes since 1.8.6:

• Remove the arrayref dependency. Unfortunately the crates.io owner was compromised.

1.8.6

version 1.8.6

Changes since 1.8.5:

• update_mmap and update_mmap_rayon (and by extension b3sum) now use seek rather than metadata to get the length of a file/mapping, and they tolerate mmap failures. That means b3sum will now memory map e.g. Linux block devices, which support mapping despite reporting length 0 in metadata. Hashing NUL files on Windows also works now, where previously it was an error unless you used --no-mmap or <. This change was originally proposed by @​nabijaczleweli.

Commits

• f3149ec version 1.8.7
• b65bcb7 add #[allow(deprecated)] annotations to fix nightly/beta warnings
• 483a220 fix warnings related to not using MAX constants
• ba02549 Codex: remove arrayref
• 77b257e version 1.8.6
• 83b1746 use seek instead of metadata to establish mmap length (#570)
• 9eac279 use vswhere to find Visual Studio in CI
• fc3d0e9 Fix path to Visual Studio toolchain in CI
• 8aa5145 a few more colons
• 6bb9773 use cargo:: build script syntax
• Additional commits viewable in compare view

Updates blake3 from 1.8.5 to 1.8.7

Release notes

Sourced from blake3's releases.

1.8.7

version 1.8.7

Changes since 1.8.6:

• Remove the arrayref dependency. Unfortunately the crates.io owner was compromised.

1.8.6

version 1.8.6

Changes since 1.8.5:

• update_mmap and update_mmap_rayon (and by extension b3sum) now use seek rather than metadata to get the length of a file/mapping, and they tolerate mmap failures. That means b3sum will now memory map e.g. Linux block devices, which support mapping despite reporting length 0 in metadata. Hashing NUL files on Windows also works now, where previously it was an error unless you used --no-mmap or <. This change was originally proposed by @​nabijaczleweli.

Commits

• f3149ec version 1.8.7
• b65bcb7 add #[allow(deprecated)] annotations to fix nightly/beta warnings
• 483a220 fix warnings related to not using MAX constants
• ba02549 Codex: remove arrayref
• 77b257e version 1.8.6
• 83b1746 use seek instead of metadata to establish mmap length (#570)
• 9eac279 use vswhere to find Visual Studio in CI
• fc3d0e9 Fix path to Visual Studio toolchain in CI
• 8aa5145 a few more colons
• 6bb9773 use cargo:: build script syntax
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

This PR aims to update the blake3 dependency to resolve a security risk involving a compromised sub-dependency. While the update is present in the Cargo.lock, the Cargo.toml file was not modified, which creates a discrepancy in dependency management and prevents the version constraint from being properly enforced. Codacy analysis indicates the project remains up to standards, but the lack of automated regression tests for the hashing logic after a library update remains a concern.

About this PR

• The PR only includes changes to the Cargo.lock file. To ensure the version constraint is formally enforced and consistent across environments, the dependency version should also be updated in Cargo.toml.
• No automated regression tests were provided or executed for this update. Given the library is central to the application's file hashing features, verification is needed to ensure the update has not introduced breaking changes or performance regressions.

Test suggestions

• Verify successful compilation and linking of the application with the new version.
• Regression test of existing file hashing features to ensure the library update did not introduce breaking changes.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify successful compilation and linking of the application with the new version.
2. Regression test of existing file hashing features to ensure the library update did not introduce breaking changes.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}