chore: update dependencies to latest versions

[braden-w]

Summary

This PR updates all dependencies to their latest versions to ensure compatibility with the latest Tauri v2.7.0 and to address deprecation warnings.

Changes

Rust Dependencies

• Tauri: Updated from 2.2.5 to 2.7.0
• tauri-plugin: Updated from 2.0.4 to 2.3.1
• tokio: Updated from 1.43.0 to 1.47.1
• serde: Updated from 1.0.217 to 1.0.219
• serde_json: Updated from 1.0.138 to 1.0.142
• reqwest: Updated from 0.12.12 to 0.12.22
• time: Updated from 0.3.37 to 0.3.41
• os_info: Updated from 3.9.2 to 3.12.0
• rand: Updated from 0.9.0 to 0.9.2
• log: Updated from 0.4.25 to 0.4.27

Code Fixes

• Fixed deprecation warning: Replaced std::panic::PanicInfo with std::panic::PanicHookInfo (deprecated in latest Rust versions)

JavaScript Dependencies

• @tauri-apps/api is already at the latest version (2.7.0)
• All TypeScript build dependencies are up to date

Testing

• ✅ Rust plugin compiles without errors
• ✅ TypeScript builds successfully
• ✅ Example project dependencies installed successfully
• ✅ No breaking changes detected

Compatibility

This update ensures the plugin is compatible with:

• Tauri v2.7.0 (latest)
• Latest Rust stable compiler
• Modern TypeScript/JavaScript tooling

These updates are important for:

1. Security: Keeping dependencies updated for latest security patches
2. Performance: Benefiting from optimizations in newer versions
3. Compatibility: Ensuring the plugin works with latest Tauri applications
4. Future-proofing: Avoiding accumulation of technical debt

Fixes #25

[cristipufu]

Hi @braden-w, thanks for your contribution. I'm a bit concerned about this change #20

[reatlat]

Hey @braden-w, thanks for your work on this! I used your fork as a base and added an extra fix for #22 (replacing tokio::spawn with tauri::async_runtime::spawn) in PR #30.

[cristipufu]

@braden-w @reatlat can you guys explain which one is the correct one? PanicHookInfo vs PanicInfo - does PanicHookInfo work on Windows? #20

[reatlat]

@cristipufu std::panic::PanicHookInfo is the official replacement for std::panic::PanicInfo — it was stabilized in Rust 1.81.0 and the old PanicInfo name became deprecated starting in Rust 1.82.0.

The rename was done to avoid confusion between std::panic::PanicInfo (used in panic hooks) and core::panic::PanicInfo (used in #[panic_handler] for no_std). They serve different roles, so Rust gave them distinct names.

It's a pure rename in the standard library — fully cross-platform, works on Windows, macOS, Linux, and every other Rust target. No platform-specific behavior.

Reference: https://doc.rust-lang.org/stable/std/panic/struct.PanicHookInfo.html

[reatlat]

@cristipufu To clarify the PanicHookInfo vs PanicInfo situation and PR #20:

PR #20 reverted PanicHookInfo back to PanicInfo because @0PandaDEV was running an older Rust toolchain on Windows (pre-1.81.0) that didn't have PanicHookInfo yet. The compiler error was no PanicHookInfo in panic (see #18) — it wasn't a platform issue, it was a Rust version issue.

So PR #20 was a workaround for an outdated toolchain, not a correct long-term fix.

Current stable Rust is 1.93.0, and PanicHookInfo has been available since 1.81.0 (released mid-2024). Anyone on a reasonably recent Rust should have it. Using the deprecated PanicInfo just silences a deprecation warning at the cost of using an outdated API.

PR #30 correctly uses PanicHookInfo.