Repository navigation
ci: pin Tauri CLI 2.12.1 to match the locked tauri crate (SNB-684) - #49
Merged
Merged
Conversation
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 <noreply@anthropic.com>
This was referenced Oct 3, 2026
Owner
Author
|
The Release bundles workflow passed with CLI 2.12.1 (run 37111418621): Linux deb/AppImage, macOS universal dmg and Windows msi/nsis. The |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes SNB-684 (Bug).
What and why
.github/workflows/release.ymlpinnedTAURI_CLI_VERSION: 2.11.5, and its own comment says to keep that equal to thetauriversion in Cargo.lock. Cargo.lock movedtaurito 2.12.1 in 8bf4c40, but the pin was not bumped with it.The matching CLI is 2.12.1. In tauri-apps/tauri, the tags
tauri-v2.12.1,tauri-cli-v2.12.1and@tauri-apps/cli-v2.12.1all point at the same release commit, 30da1fd. That release also containstauri-utils-v2.10.1andtauri-build-v2.7.1, which are the versions in our Cargo.lock.npm view @tauri-apps/cli versionslists 2.12.1.Behaviour
Release bundles are now built by the CLI released with the tauri crate we compile against. No source or config changes; the comment stays true.
Verification
release.yml, so the "Release bundles" workflow runs on it and builds the deb, AppImage, dmg and Windows bundles with CLI 2.12.1. That run is the check that matters.cargo check --workspace --all-targets --all-features0 warnings; clippy-D warningsclean; fmt clean;cargo test --workspace254 passed, 1 ignored, 0 failed.