chore: bump @choochmeque/tauri-plugin-notifications-api from 0.5.0-rc.11 to 0.5.0-rc.13

[dependabot]

Bumps @choochmeque/tauri-plugin-notifications-api from 0.5.0-rc.11 to 0.5.0-rc.13.

Release notes

Sourced from @​choochmeque/tauri-plugin-notifications-api's releases.

v0.5.0-rc.13

Adds click handling to the notify-rust desktop backend and raises the MSRV to 1.93.

⚠️ Breaking changes

• MSRV raised from 1.90 to 1.93; build with Rust 1.93 or newer (2400cdb)

Changes

• Desktop (notify-rust backend — always on Linux, opt-in on macOS/Windows via the notify-rust feature): onNotificationClicked now fires when the user activates a notification. While a listener is subscribed, macOS and Linux declare a "default" action to arm the wait, and a waiter emits notificationClicked with the same { id, data } payload the native backends send. Only notifications shown while a listener is subscribed are observed; dismissals and expiry emit nothing (#284)
• Desktop (notify-rust backend): set_click_listener_active records the subscription instead of failing with "Click listeners are not supported with notify-rust" (#284)
• Linux: observed notifications are removed from the active map once they resolve, so active() no longer reports notifications that are already gone (6f7eb8e)
• Linux: tracked notification handles are shared through an Arc and closed with close_async, so cancel / cancelAll keep working while a click waiter holds the same handle (#284)
• Windows (native WinRT backend): no behavior change. windows.rs was reworked for clippy and style — let-chains, explicit crate::models imports, i64::from conversions, &raw const for the CLSID, inline format args, earlier lock-guard release in register_action_types and close_push_channel, and a private field rename _com_cookie → com_cookie (now read back). "Fix logic for checking action ID validity in NotificationsBuilder" (8a7d6e4) is .ok().is_some_and(..) → .is_ok_and(..), which is semantically identical
• The plugin now depends on tauri with default-features = false, so it no longer pulls wry in on its own; the iOS target keeps features = ["wry"]. Consumers whose app already enables the features it needs are unaffected; builds that don't need a webview no longer get one from this edge (#280 @​eleboucher)

Build & tooling

• CI moved to the shared Choochmeque/reusable-actions@v1 workflows for checks, tests and build-demo, which gate jobs by the paths a PR touches (#321)
• Superseded CI runs are cancelled per workflow and ref; push CI runs on main only, where each commit gets its own uncancellable run (#320)
• Unit tests for the notify-rust click-response mapping — is_activation over Default / Action("default") / other actions / every close reason, and the click_payload JSON shape (0c45e5b)
• Example app gained a notify-rust feature, so pnpm tauri dev --features notify-rust selects that backend instead of the native one (e305426)

Dependencies

• tauri 2.11.4 → 2 (default-features = false), notify-rust 4.11 → 4.18
• android: androidx.appcompat 1.7.1 → 1.8.0, jackson-databind 2.22.0 → 2.22.2, firebase-bom 34.15.0 → 34.18.0, org.json 20260522 → 20260814
• npm (dev): prettier 3.9.4 → 3.9.6, rollup 4.62.2 → 4.63.1, vitest 4.1.9 → 4.1.11, @​vitest/coverage-v8 4.1.9 → 4.1.11, vite pinned as a direct devDependency at 8.2.2, esbuild 0.27.7 → 0.28.2 — the last two to clear transitive advisories (#317, #318, #322)
• actions/setup-node 6 → 7 (#264), pnpm/action-setup 6 → 6.0.10
• example app: @​sveltejs/kit 2.68.0 → 2.70.3, @​sveltejs/vite-plugin-svelte 7.1.2 → 7.3.0, svelte 5.56.4 → 5.57.0, svelte-check 4.7.1 → 4.7.6, vite 8.1.0 → 8.2.2, @​tauri-apps/plugin-opener 2.5.4 → 2.5.5, @​choochmeque/tauri-windows-bundle 0.1.26 → 0.1.28
• example app (Rust): tauri 2.11.2 → 2.11.5, notify-rust 4.17.0 → 4.18.0
• example app (Android): androidx.webkit 1.16.0 → 1.17.0, androidx.appcompat 1.7.1 → 1.8.0

Full changelog: Choochmeque/tauri-plugin-notifications@v0.5.0-rc.11...v0.5.0-rc.13

Commits

• 45f9660 Bump version to 0.5.0-rc.13
• dbf5453 Merge pull request #325 from Choochmeque/ci/publish-node
• ae25310 Pin the npm self-update to major 11
• d492a74 Publish on Node 24
• 5ae2353 Bump version to 0.5.0-rc.12
• 4fd41e3 Merge pull request #323 from Choochmeque/dependabot/npm_and_yarn/examples/not...
• bfe4bd1 Merge pull request #322 from Choochmeque/dependabot/npm_and_yarn/vite-8.2.2
• ca35304 Bump svelte from 5.56.10 to 5.57.0 in /examples/notifications-demo
• 604d287 Bump vite from 7.3.6 to 8.2.2
• 78ad54e Merge pull request #284 from Choochmeque/notify-rust-click-handler
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
blockwire	Ready	Preview	Sep 15, 2026 7:51pm UTC

[dependabot]

Superseded by #87.