[dependabot]

Bumps the cargo group with 7 updates in the / directory:

Package	From	To
serde_json	1.0.151	1.0.154
thiserror	2.0.20	2.0.21
trash	5.2.8	5.2.9
tauri	2.11.5	2.11.6
tauri-plugin-global-shortcut	2.3.2	2.4.1
libc	0.2.189	0.2.190
tauri-build	2.6.3	2.7.3

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

• Support preserve_order in no_std builds (#1333, thanks @​razmser)

v1.0.153

• Report invalid UTF-8 at the first bad byte (#1345, thanks @​00200200)

v1.0.152

• Preserve sign of -0 in arbitrary_precision mode (#1346, thanks @​yuxi-liu-wired)
• Fix comparison of large non-integer values with f32::INFINITY (#1347, thanks @​yuxi-liu-wired)

Commits

• 20572a6 Release 1.0.154
• a91bfaf Fix RandomState links in map documentation
• 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
• 4b2d726 Release 1.0.153
• 83335ee Touch up PR 1345
• 4b4810a Resolve range_plus_one pedantic clippy lint
• 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
• 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
• c9f1e3b Release 1.0.152
• 854fc70 Touch up PR 1347
• Additional commits viewable in compare view

Updates thiserror from 2.0.20 to 2.0.21

Release notes

Sourced from thiserror's releases.

2.0.21

• Fix parsing of generic unit variants in display expressions (#459)

Commits

• b1827ee Release 2.0.21
• 58037b5 Merge pull request #459 from dtolnay/turbofish
• f82a0cf Keep track of nested turbofish depth
• 72ea492 Raise required compiler to Rust 1.77
• 72eea0d Resolve io_other_error clippy lint in tests
• 07f09a2 Raise required compiler to Rust 1.74
• 2715388 Update ui test suite to nightly-2026-09-22
• 5a306c7 Update ui test suite to nightly-2026-09-05
• ef9383b Update ui test suite to nightly-2026-08-22
• 8336b84 Update ui tests for version 2.0.20
• See full diff in compare view

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

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

Updates tauri-plugin-global-shortcut from 2.3.2 to 2.4.1

Release notes

Sourced from tauri-plugin-global-shortcut's releases.

global-shortcut-js v2.4.1

[2.4.1]

• fc18d055 (#3683) Release the shortcuts lock before running shortcut handlers, so a handler that calls back into the plugin, or pumps messages that dispatch another shortcut event, no longer deadlocks the app.

npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm warn publish errors corrected:
npm warn publish "repository" was changed from a string to an object
npm warn publish "repository.url" was normalized to "git+https://github.com/tauri-apps/plugins-workspace.git"
npm notice
npm notice 📦  @tauri-apps/plugin-global-shortcut@2.4.1
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 3.8kB README.md
npm notice 3.5kB dist-js/index.cjs
npm notice 3.3kB dist-js/index.d.ts
npm notice 3.4kB dist-js/index.js
npm notice 666B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-global-shortcut
npm notice version: 2.4.1
npm notice filename: tauri-apps-plugin-global-shortcut-2.4.1.tgz
npm notice package size: 3.7 kB
npm notice unpacked size: 15.6 kB
npm notice shasum: b5d53b422217eacf53ad630c586a8c3a72cd7d0e
npm notice integrity: sha512-NVCoQ0ShDFncs[...]lvVOG7tMr/e8g==
npm notice total files: 6
npm notice
npm notice npm tokens that bypass 2FA are being restricted for account changes and direct publishing. Learn how to prepare: https://gh.io/npm-gat-bypass2fa-deprecation
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=3189615918
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-global-shortcut@2.4.1

global-shortcut v2.4.1

[2.4.1]

• fc18d055 (#3683) Release the shortcuts lock before running shortcut handlers, so a handler that calls back into the plugin, or pumps messages that dispatch another shortcut event, no longer deadlocks the app.

... (truncated)

Commits

• d66aa6f publish new versions (#2822)
• 6f34587 fix(single-instance): disable dbus name replacement (#2860)
• 708fa4e chore(deps): update dependency eslint-config-prettier to v10.1.8 (#2858)
• b729203 fix(upload): fix download() locks main thread on Android (#2838)
• 2f9c71a chore(deps): update dependency rollup to v4.45.1 (#2850)
• 80d4d8e chore(deps): update eslint monorepo to v9.31.0 (v2) (#2839)
• e7a98b0 chore(deps): update dependency typescript-eslint to v8.37.0 (#2848)
• 44a1f65 fix(fs): writeFile create file by default (#2846)
• 6210cd3 chore(deps): update dependency rollup to v4.45.0 (#2841)
• 467f07b chore(deps): update dependency vite to v7 (v2) (#2800)
• Additional commits viewable in compare view

Updates libc from 0.2.189 to 0.2.190

Release notes

Sourced from libc's releases.

0.2.190

There is now a single config for enabling 64-bit time_t: libc_unstable_time64. This can be set unconditionally; it opts in to 64-bit time_t on the following platforms that use 32-bit by default:

• 32-bit Linux-GNU
• 32-bit Linux-uClibc
• 32-bit Linux-musl. Note that setting this flag also enables some other changes that happend in musl v1.2.
• 32-bit Windows-GNU
• ESP-IDF (all targets with this environment are 32-bit)

Most other 32-bit platforms are either already using 64-bit time_t, or are considered legacy and will not be gaining support from their upstream maintainers.

You can enable this using RUSTFLAGS:

RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...

Note that there may still be some changes to features gated by this config option, hence "unstable" in its name. In the near future we will rename it to just libc_time64. Until then, please test it out and report any bugs you find!

Support

• Add initial support for HelenOS (#4355)

Added

We are slowly filling out the Default implementations, to reduce the need for mem::zeroed() in user code:

• Unix: Implement Default for a number of structs, especially on Apple platforms (#5576)
• Linux, NetBSD: Give statvfs a Default impl (#5583)
• Linux: Add Default to a linux/can.rs structs (#5257)

Other additions:

• Expose the libc_unstable_time64 cfg (#5411)
• Android, Glibc: Add pthread_gettid_np (#5359)
• Android: Add RTLD_NEXT (#5323)
• Android: Add reuseport BPF socket options (#5366)
• Apple: Add TCP header flags, options and SACK limits (#5358)
• Apple: Add NET_RT_DUMP2 (#5442)
• Apple: Add posix_spawn_file_actions_add(f)chdir(_np) (#5558)
• BSD: Add BPF_WORDALIGN (#5320)
• BSD: Add lchmod and lchflags where supported (#5400)
• BSD: Add minherit and related constants (#4849)
• Docs: Add more links to public headers and manual pages (#5407), (#5485)

... (truncated)

Changelog

Sourced from libc's changelog.

0.2.190 - 2026-10-02

There is now a single config for enabling 64-bit time_t: libc_unstable_time64. This can be set unconditionally; it opts in to 64-bit time_t on the following platforms that use 32-bit by default:

• 32-bit Linux-GNU
• 32-bit Linux-uClibc
• 32-bit Linux-musl. Note that setting this flag also enables some other changes that happend in musl v1.2.
• 32-bit Windows-GNU
• ESP-IDF (all targets with this environment are 32-bit)

Most other 32-bit platforms are either already using 64-bit time_t, or are considered legacy and will not be gaining support from their upstream maintainers.

You can enable this using RUSTFLAGS:

RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...

Note that there may still be some changes to features gated by this config option, hence "unstable" in its name. In the near future we will rename it to just libc_time64. Until then, please test it out and report any bugs you find!

Support

• Add initial support for HelenOS (#4355)

Added

We are slowly filling out the Default implementations, to reduce the need for mem::zeroed() in user code:

• Unix: Implement Default for a number of structs, especially on Apple platforms (#5576)
• Linux, NetBSD: Give statvfs a Default impl (#5583)
• Linux: Add Default to a linux/can.rs structs (#5257)

Other additions:

• Expose the libc_unstable_time64 cfg (#5411)
• Android, Glibc: Add pthread_gettid_np (#5359)
• Android: Add RTLD_NEXT (#5323)
• Android: Add reuseport BPF socket options (#5366)
• Apple: Add TCP header flags, options and SACK limits (#5358)
• Apple: Add NET_RT_DUMP2 (#5442)
• Apple: Add posix_spawn_file_actions_add(f)chdir(_np) (#5558)
• BSD: Add BPF_WORDALIGN (#5320)
• BSD: Add lchmod and lchflags where supported (#5400)
• BSD: Add minherit and related constants (#4849)

... (truncated)

Commits

• 7b0ab55 ci: Rename publish_0.2.yml to release.yaml
• ac85dde ci: Sync release permissions with main
• 8f8cd20 libc: Release 0.2.190
• 052c6e6 changelog: Fix an incorrect commit link
• ea19fd7 test: Remove explicit libc version
• 6dbf3a2 dragonfly: Move INHERIT_ZERO to the freebsd module
• 8a64766 apple: add posix_spawn_file_actions_add(f)chdir(_np)
• 28de514 linux, netbsd: Give statvfs a Default impl
• a58a95f cygwin: Change POSIX_SPAWN_* flags to c_short
• d175264 apple: timeval32 is exhaustive
• Additional commits viewable in compare view

Updates tauri-build from 2.6.3 to 2.7.3

Release notes

Sourced from tauri-build's releases.

tauri-build v2.7.3

Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 1314 security advisories (from /home/runner/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (1045 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:     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
Version:   0.25.1
Warning:   unmaintained
Title:     ttf-parser is unmaintained
Date:      2026-06-28
ID:        RUSTSEC-2026-0192
URL:       https://rustsec.org/advisories/RUSTSEC-2026-0192
warning: 4 allowed warnings found

[2.7.3]

Enhancements

... (truncated)

Commits

• 59b63ab Apply Version Updates From Current Changes (#16255)
• 55883af fix(bundler): Update rpm-rs to 0.30 (#15639)
• 744ff2b chore(deps): bump rustls to 0.23.46
• c95be46 fix(cli): xcode-script tauri CWD rewrite (#16287)
• dc637db chore: add missing api change file (#16260)
• b948762 fix(macos-sign): import the signing certificate as an explicit pkcs12 (fix: #...
• 7b673dd fix(core): drop late mobile plugin responses instead of panicking (#16146)
• 5a61498 fix(bundler): keep script stderr in errors and hint at the Finder permission ...
• 5a3cbfc fix(macos-codesign): Inline apple-codesign code (#16279)
• 141d1c0 fix(acl): resolve permission files after the target dir is moved (#16199)
• 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

[dependabot]

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