build(deps): bump the cargo group with 2 updates

[dependabot]

Bumps the cargo group with 2 updates: trash and tauri.

Updates trash from 5.2.8 to 5.2.9

Release notes

Sourced from trash's releases.

v5.2.9

This is a bug-fix release, where unfortunately I forgot to make the needed edits to the commit message for all of them to automatically show up here. Check the "Commit Details" section instead for everything that went into it.

Bug Fixes

• fall back to the home trash when per-volume trash cannot be created The spec (v1.0, section "Trash directories") says an implementation "MUST either trash the file into the user's home trash or refuse to trash it" when both $topdir/.Trash/$uid and $topdir/.Trash-$uid are unavailable. Until now the crate took the "refuse" branch, returning a PermissionDenied error whenever the mount-point root was not writable by the calling user - the common case on every partition whose root is owned by root.

  Catch PermissionDenied from execute_on_mounted_trash_folders and fall back to move_to_trash with the home trash, which already handles cross-device copies via copy+delete.

Commit Statistics

• 8 commits contributed to the release.
• 5 days passed between releases.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

• Uncategorized
  • Prepare changelog prior to release (deaf4de)
  • Merge pull request #151 from jaroslavpachola/home-trash-fallback (f99e82e)
  • Review (18cbe14)
  • Fall back to the home trash when per-volume trash cannot be created (50ede33)
  • Merge pull request #150 from ggand0/fix-windows-unc-parsing-name (29ad086)
  • Review (e57c153)
  • Keep the root backslash when rebuilding shell parsing names (e99afbd)
  • Rebuild verbatim paths before handing them to the shell on Windows (ba1d72f)

Changelog

Sourced from trash's changelog.

5.2.9 (2026-09-13)

This is a bug-fix release, where unfortunately I forgot to make the needed edits to the commit message for all of them to automatically show up here. Check the "Commit Details" section instead for everything that went into it.

Bug Fixes

• fall back to the home trash when per-volume trash cannot be created The spec (v1.0, section "Trash directories") says an implementation "MUST either trash the file into the user's home trash or refuse to trash it" when both $topdir/.Trash/$uid and $topdir/.Trash-$uid are unavailable. Until now the crate took the "refuse" branch, returning a PermissionDenied error whenever the mount-point root was not writable by the calling user - the common case on every partition whose root is owned by root.

  Catch PermissionDenied from execute_on_mounted_trash_folders and fall back to move_to_trash with the home trash, which already handles cross-device copies via copy+delete.

Commit Statistics

• 8 commits contributed to the release.
• 5 days passed between releases.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

• Uncategorized
  • Prepare changelog prior to release (deaf4de)
  • Merge pull request #151 from jaroslavpachola/home-trash-fallback (f99e82e)
  • Review (18cbe14)
  • Fall back to the home trash when per-volume trash cannot be created (50ede33)
  • Merge pull request #150 from ggand0/fix-windows-unc-parsing-name (29ad086)
  • Review (e57c153)
  • Keep the root backslash when rebuilding shell parsing names (e99afbd)
  • Rebuild verbatim paths before handing them to the shell on Windows (ba1d72f)

Commits

• 54e0a2d Release trash v5.2.9
• deaf4de prepare changelog prior to release
• f99e82e Merge pull request #151 from jaroslavpachola/home-trash-fallback
• 18cbe14 review
• 50ede33 fix: fall back to the home trash when per-volume trash cannot be created
• 29ad086 Merge pull request #150 from ggand0/fix-windows-unc-parsing-name
• e57c153 review
• e99afbd Keep the root backslash when rebuilding shell parsing names
• ba1d72f Rebuild verbatim paths before handing them to the shell on Windows
• See full diff in compare view

Updates tauri from 2.11.5 to 2.11.6

Release notes

Sourced from tauri's releases.

tauri v2.11.6

Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 1251 security advisories (from /home/runner/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (1075 crate dependencies)
Crate:     fxhash
Version:   0.2.1
Warning:   unmaintained
Title:     fxhash - no longer maintained
Date:      2025-09-05
ID:        RUSTSEC-2025-0057
URL:       https://rustsec.org/advisories/RUSTSEC-2025-0057
Crate:     paste

Version:   1.0.15

Warning:   unmaintained

Title:     paste - no longer maintained

Date:      2024-10-07

ID:        RUSTSEC-2024-0436

URL:       https://rustsec.org/advisories/RUSTSEC-2024-0436
Crate:     rustls-pemfile

Version:   1.0.4

Warning:   unmaintained

Title:     rustls-pemfile is unmaintained

Date:      2025-11-28

ID:        RUSTSEC-2025-0134

URL:       https://rustsec.org/advisories/RUSTSEC-2025-0134
Crate:     rustls-pemfile

Version:   2.2.0

Warning:   unmaintained

Title:     rustls-pemfile is unmaintained

Date:      2025-11-28

ID:        RUSTSEC-2025-0134

URL:       https://rustsec.org/advisories/RUSTSEC-2025-0134
Crate:     rustybuzz

Version:   0.20.1

Warning:   unmaintained

Title:     rustybuzz is unmaintained

Date:      2026-07-11

ID:        RUSTSEC-2026-0206

URL:       https://rustsec.org/advisories/RUSTSEC-2026-0206
Crate:     ttf-parser

</tr></table>

... (truncated)

Commits

• 9452dde fix audit
• 7c2fe9f run covector version
• 7d71a8a add publish-hotfix workflow
• 5a87bab Merge commit from fork
• e901f1d Merge commit from fork
• See full diff 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.