build: bump Rust version to 1.94.0#9
Merged
Conversation
jjhafer
approved these changes
May 29, 2026
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.
Summary
Bumps the project's Rust version to 1.94.0 to match the updated Silvermine standard (silvermine/silvermine-info#47), plus dependency-spec cleanup for the example app.
Toolchain bump
rust-toolchain.tomlchannel →1.94.0rust-versionin the workspaceCargo.tomland the example app.github/workflows/ci.yml)1.89+→1.94+)Example app dependency alignment
The example app was the only one of the Silvermine Tauri plugin examples that pinned dependencies with the
=comparison operator (tauri,serde,tauri-build) and did not track aCargo.lock. Because tauri's own runtime crates use caret ranges, a fresh resolve drifted to incompatible versions (tauri 2.10.3againsttauri-runtime 2.11.2) and pulledbitflags 2.12.0, which overflows the macro recursion limit indispatch2.=operators to match the sibling examples and the Silvermine standard (which forbids comparison requirements).Cargo.lockso the example builds reproducibly, as the audio and connectivity examples already do.Verification
npm run standardspasses (markdownlint, clippy, fmt, eslint, commitlint, node check).