Bump trash from 5.2.8 to 5.2.9 in /src-tauri

[dependabot]

Bumps 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

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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.