chore(deps): update rust crate trash to v5.2.9 - #1006
Merged
Merged
Conversation
JohnTitor
approved these changes
Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.2.7→5.2.9Release Notes
ArturKovacs/trash (trash)
v5.2.9Compare Source
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
Commit Details
view details
deaf4de)f99e82e)18cbe14)50ede33)29ad086)e57c153)e99afbd)ba1d72f)v5.2.8Compare Source
Chore
Commit Statistics
Commit Details
view details
836b6e5)6bd5e33)2876333)Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.