chore(deps-dev): Bump @tauri-apps/cli from 2.11.2 to 2.11.4

[dependabot]

Bumps @tauri-apps/cli from 2.11.2 to 2.11.4.

Release notes

Sourced from @​tauri-apps/cli's releases.

@​tauri-apps/cli v2.11.4

[2.11.4]

Bug Fixes

• 67ffa192a (#15596 by @​FabianLars) Fixed an issue in the AppImage bundler that caused the /.desktop and .DirIcon files to be absolute symlinks instead of relative symlinks which caused problems with AppImage installers like AppManager.

Dependencies

• Upgraded to tauri-cli@2.11.4

@​tauri-apps/cli v2.11.3

[2.11.3]

Bug Fixes

• 50b0237ed (#15549 by @​Legend-Master) Escape special characters in productName when generating Android strings.xml

• 728c8d4a5 (#15473 by @​Legend-Master) Skip building bundles when using tauri android run

• be0cb0d43 (#15344 by @​raglady) Fix NDK_HOME environment variable not honored when set

• ed8fd411f (#15552 by @​Legend-Master) Make ureq_proto show trace level logs only on -vvv instead of -vv

• fca4a31f9 (#15454 by @​fallintoplace) Fix tauri migrate generating invalid namespace imports for aliased pluginified imports from @tauri-apps/api.

  Inputs like import { cli as superCli } from "@tauri-apps/api" now migrate to import * as superCli from "@tauri-apps/plugin-cli" instead of producing invalid ESM syntax. The migration tests also reparse migrated JS, Svelte, and Vue output so syntax regressions are caught directly.

Dependencies

• Upgraded to tauri-cli@2.11.3

Commits

• 8909f22 apply version updates (#15598)
• 67ffa19 fix(bundler): make .desktop and .DirIcon relative symlinks (#15596)
• c5c8b2b docs(readme): desktop platforms -> operating systems, closes #15589
• 80d437f fix(#15580): bump memmap2 (#15587)
• 469ecc8 test: regenerate stale macOS acl snapshot for has_app_acl (#15576)
• 5be0cb8 fix(ci): change strip to debuginfo for cloudflare worker (#15574)
• 4bbd497 chore(deps): bump cloudflare worker versions (#15573)
• 5712549 chore(deps): update dependency rollup to v4.62.0 (#15551)
• c8faedf ci: test on node 20,22 instead of node 18,20
• 3641e26 refactor: simplify menu code (#15559)
• 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 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)

[oratis]

Reviewed and verified locally against current main.

Same-major bump of a build tool. Version alignment across the three places Tauri versions live is fine:

	version
@tauri-apps/cli (this PR)	2.11.4
tauri crate (Cargo.lock)	2.11.2
@tauri-apps/api (installed via ^2.0.0)	2.11.0

Same minor throughout, which is what Tauri asks for — a CLI ahead of the crate by a patch is supported.

Verified the CLI actually reads this project: tauri info under 2.11.4 parses tauri.conf.json without complaint and resolves every plugin crate. (Its @tauri-apps/api: not installed! line is a pnpm-detection artifact — it warns no lock files found, defaulting to npm because the workspace lockfile is at the repo root, and the package is in fact installed at 2.11.0. Pre-existing, unrelated to this bump.)

Scope, stated honestly: the CLI is invoked in exactly two places — scripts/sign-and-notarize.sh (tauri build) and the tauri signer generate step in docs/RELEASING.md. CI never runs either; the "Desktop Rust check + test" job drives cargo directly. So a green CI here is not evidence the bundler half still works — the first real exercise is the next build-mac run. Config parsing is the most I can check without an Apple-credentialed release.

Full gate on the merged result: typecheck, lint, format, docs clean; 1671 tests pass, 19 skipped.