mirror of
https://github.com/NanmiCoder/cc-haha
synced 2026-07-17 13:13:35 +08:00
c13fa75c3b
The release script regenerated Cargo.lock after Tauri 2.11 became available, while the desktop Bun lock still resolves @tauri-apps/api and CLI to 2.10.1. Tauri's build preflight rejects that major/minor mismatch on every platform, so the Rust Tauri release stack is now pinned to the 2.10 combination already used by the previous successful release. Constraint: v0.1.9 must keep the existing desktop Bun lock and JS Tauri packages at 2.10.1 Constraint: scripts/release.ts runs cargo generate-lockfile during release preparation Rejected: Upgrade JS @tauri-apps packages during the release fix | larger dependency surface and unnecessary for the failed workflow Rejected: Pin only the tauri crate | cargo still selected tauri-runtime 2.11.0, causing Rust API type mismatches Confidence: high Scope-risk: narrow Directive: Keep Rust and JS Tauri major/minor versions aligned before moving release tags Tested: gh run view 25217609687 --log-failed Tested: cd desktop/src-tauri && cargo generate-lockfile Tested: cd desktop && bunx tauri build --target aarch64-apple-darwin --config src-tauri/tauri.release-ci.json --no-bundle Tested: cd desktop/src-tauri && cargo check Not-tested: Full GitHub Actions matrix after retag
25 lines
576 B
TOML
25 lines
576 B
TOML
[package]
|
|
name = "claude-code-desktop"
|
|
version = "0.1.9"
|
|
edition = "2021"
|
|
|
|
[lib]
|
|
name = "claude_code_desktop_lib"
|
|
crate-type = ["staticlib", "cdylib", "rlib"]
|
|
|
|
[build-dependencies]
|
|
tauri-build = { version = "=2.5.6", features = [] }
|
|
|
|
[dependencies]
|
|
tauri = { version = "=2.10.3", features = ["tray-icon"] }
|
|
tauri-runtime = "=2.10.1"
|
|
tauri-runtime-wry = "=2.10.1"
|
|
tauri-plugin-shell = "2"
|
|
tauri-plugin-dialog = "2"
|
|
tauri-plugin-process = "2"
|
|
tauri-plugin-updater = "2"
|
|
serde = { version = "1", features = ["derive"] }
|
|
serde_json = "1"
|
|
anyhow = "1.0.102"
|
|
portable-pty = "0.9.0"
|