chore(tauri-plugin-devtools): release v2.2.3

[github-actions]

🤖 New release

• tauri-plugin-devtools: 2.2.2 -> 2.2.3

Changelog

2.2.3 - 2026-10-02

Other

• update Cargo.toml dependencies

---

This PR was generated with release-plz.

[netlify]

✅ Deploy Preview for cn-devtools-app canceled.

Name	Link
🔨 Latest commit	ed8b8f2
🔍 Latest deploy log	https://app.netlify.com/projects/cn-devtools-app/deploys/6abf9ed548fbf90008e1edbf

[james-crabnebula]

Closing: same situation as #426. Nothing in crates/devtools, the workspace Cargo.toml or Cargo.lock has changed since tag tauri-plugin-devtools-v2.2.2 (git diff tauri-plugin-devtools-v2.2.2..main -- crates/devtools Cargo.toml Cargo.lock is empty; the published 2.2.2 crate is byte-identical to main). Merging would publish an identical crate as 2.2.3 with a changelog line that describes no change.

Cause, from the release-plz run log (run 37004800124, job release-plz-v2): release-plz takes tauri-plugin-devtools 3.0.0-alpha.0 from crates.io as the registry baseline for the v2 crate, compares it with local 2.2.2, sees the v3 manifest's different dependencies, and emits the synthetic "update Cargo.toml dependencies" entry; with semver_check = false it picks a patch bump. The same run that published 2.2.2 on 2026-09-29 opened #426 for 2.2.3 in the same minute. This will recur after every push to main until the v2 line is baselined against its own version rather than the highest published one.