Repository navigation
chore: update all dependencies, pin them exactly and require Rust 1.90 - #38
Merged
Merged
Conversation
This was referenced Oct 12, 2026
…d-ci # Conflicts: # .github/workflows/ci.yml # README.md # src-tauri/Cargo.toml
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.
Brings every dependency to its latest release, pins the manifests to exact versions, and makes CI lint and test the Rust code on all three platforms.
Dependencies
cargo update: the same lockfile refresh as Dependabot chore(deps): bump the cargo-minor group across 1 directory with 159 updates #36 (tauri 2.12.3, wry 0.57, reqwest 0.13.5, serde 1.0.229, ...), one step newer where a release landed since, refreshed again on 2026-10-14 (rustls 0.23.46, tokio 1.53.3, schemars 1.2.3, deranged, equivalent, rustls-native-certs). The five cratescargo updatestill reports behind latest (toml 0.8.2, toml_datetime, toml_edit, brotli-decompressor, generic-array) are held by version requirements in system-deps, brotli and crypto-common, not by this manifest.npm outdated --allnow lists only TypeScript 7, which is held back as explained below.rust-versionmoves from 1.88 to 1.90. The MSRV job on chore(deps): bump the cargo-minor group across 1 directory with 159 updates #36 failed withtauri@2.12.2 requires rustc 1.90(also muda 0.20, tauri-build, tauri-runtime, tauri-utils; uuid 1.28 needs 1.89). The comment above it and the README now say 1.90.@tauri-apps/api2.12.3 (matches the tauri crate),@tauri-apps/cli2.12.2, and TypeScript 5.9.3 to 6.0.3, the newest major svelte-check accepts.svelte-checkpasses with 0 errors and 0 warnings on 6.0.3.npm cifails on 7 (the ERESOLVE in chore(deps-dev): bump typescript from 5.9.3 to 7.0.2 #18), and svelte-check 4.7 only runs 7 through an experimental--tsgomode that needs TypeScript 6 installed alongside..github/dependabot.ymlnow ignores semver-major TypeScript updates, with a comment saying when to remove the ignore.Exact pins and crate metadata
src-tauri/Cargo.toml: every dependency, dev-dependency and build-dependency is pinned to the full version inCargo.lock(tauri 2.12.3, tauri-build 2.7.2, steamworks-sys 0.13.0, libc 0.2.190, winreg 0.56.0, windows-sys 0.61.2, ...), features unchanged.package.json: exact versions, no^, matchingpackage-lock.json.descriptionno longer says Linux only,authorsis Project Colony,repositorypoints at this repo.licenseisGPL-3.0-onlyin both manifests, replacing the deprecatedGPL-3.0SPDX alias. The README already gaveGPL-3.0-onlyas the identifier; the or-later question is unchanged.[profile.release]:lto = "thin"andstrip = "symbols", as in the Colony release profile.codegen-units = 1,opt-level = 3andpanic = "unwind"(with its comment) stay.CI
lts/*instead of Node 20, which is end of life.actions/setup-nodemoves from v7.0.0 to v7.1.0 inci.ymlandrelease.yml. Every other action is already on its latest release.dtolnay/rust-toolchainmoves from89b12181(stable branch, before the action's input-handling fix) toe2a55d2fon master withtoolchain: stable, the pinrelease.ymlalready uses. The MSRV job keeps its owntoolchaininput.cargo clippy --all-targets -- -D warnings, which replacescargo check, andcargo test. Windows now runs the unit tests too.cargo testand the "Start without libsteam_api installed" build from fix: let the Linux and macOS binaries start without Valve's Steamworks library installed #37 now pass--targetlike Clippy, so all three sharetarget/<triple>/debug.sort_by_keywithReversein the fuzzy search, a negation instead of== falseinstart_client, and build.rs now generates the 1052 Steamworks function names as astaticrather than aconst(clippy::large_const_arrays).Merged with #35
#35 landed first, so main is merged into this branch. The three conflicts are resolved as planned:
dirsis pinned to 7.0.0 (current, and it only changespreference_diron Windows, which SAM does not call),ci.ymlkeeps #35's Frontend checks step before Clippy, and the README keeps #35's checks section with Rust 1.90.cargo updateafter the merge found nothing newer.Verification
cargo clippy --locked --all-targets -- -D warningson Linux: clean.cargo test --lockedon Linux: 4 passed, including the test that calls through the Steamworks stubs.cargo update --dry-run: nothing left to update within the pins.cargo clippy --locked --all-targets -- -D warningsclean,cargo test --locked4 passed,npm run buildwith svelte-check at 0 errors and 0 warnings.npm ci,npm run build(svelte-check, then vite build): 0 errors, 0 warnings.cargo clippy --locked --all-targets -- -D warningsclean,npm run build,check:i18n,check:style,npm testandcheck:vendoredpass.Supersedes #36. #18 is closed with a pointer here.