From 93c47b72ede8bf5fd5302e1414ba171c62f65b11 Mon Sep 17 00:00:00 2001 From: setavenger Date: Sat, 3 Oct 2026 08:52:03 +0000 Subject: [PATCH] ci: pin Tauri CLI 2.12.1 to match the locked tauri crate (SNB-684) release.yml pinned TAURI_CLI_VERSION 2.11.5, but Cargo.lock moved the tauri crate to 2.12.1 in 8bf4c40, against the workflow's own rule to keep the two equal. tauri 2.12.1 was released from the same commit (30da1fd in tauri-apps/tauri) as tauri-cli and @tauri-apps/cli 2.12.1, together with tauri-utils 2.10.1 and tauri-build 2.7.1, which are also the versions in Cargo.lock. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 4536b02..49cb379 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -33,7 +33,7 @@ defaults: env: # Tauri releases the CLI in lockstep with the `tauri` crate; keep this equal # to the `tauri` version in Cargo.lock. - TAURI_CLI_VERSION: 2.11.5 + TAURI_CLI_VERSION: 2.12.1 PROTOC_VERSION: "36.2" CARGO_TERM_COLOR: always