Skip to content

Keep the Tauri crates on the same minors as their npm packages, and check it - #44

Merged
EarMaster merged 1 commit into
mainfrom
develop
Nov 11, 2026
Merged

EarMaster merged 1 commit into
mainfrom
develop

Conversation

@EarMaster

Copy link
Copy Markdown
Owner

v1.12.2's release failed on all six platforms: tauri build refused to start because five plugins were a minor apart between npm and Rust. The Dependabot commit's npm update had moved @tauri-apps/plugin-autostart, -deep-link, -dialog, -opener and -process ahead, and their crates stayed where they were. Nothing before tauri build compares the two, so tests, tsc and cargo check were all green, and only the release itself found out. The same release had also left package-lock.json on 1.12.1, because the version bump never wrote that file.

  • The five crates move to the npm side's minors: autostart 2.7.0, deep-link 2.6.3, dialog 2.8.4, opener 2.7.2, process 2.4.0, all past the 7-day cooldown. That drops 61 old crates from Cargo.lock, among them rand 0.7.3, one of the open Dependabot alerts, and the unmaintained fxhash.
  • package.json and Cargo.toml now state the versions that are actually locked, rather than floors several minors below them.
  • scripts/check-lockfiles.mjs (npm run check:lockfiles) fails when an @tauri-apps package and its crate are on different minors, when package-lock.json no longer matches package.json, or when the six places that carry the version disagree. With --staged it reads the git index, which is how /commit's preflight runs it. The Tests workflow runs it first, in the Changelog job, where it takes seconds instead of a release matrix.
  • cargo test and clippy run with --locked, so a Cargo.lock that no longer fits Cargo.toml fails CI instead of being re-resolved on the runner.

Against the commit before this one, the check reports exactly the five pairs from the release log plus the stale lockfile version. On this tree it passes, clippy is clean, 237 Rust tests pass, and a local tauri build gets through the version check and builds a release binary.

…heck it

v1.12.2's release failed on all six platforms: tauri build refused to start
because five plugins were a minor apart between npm and Rust. The Dependabot
commit's npm update had moved @tauri-apps/plugin-autostart, -deep-link,
-dialog, -opener and -process ahead, and their crates stayed where they were.
Nothing before tauri build compares the two, so tests, tsc and cargo check
were all green, and only the release itself found out. The same release had
also left package-lock.json on 1.12.1, because the version bump never wrote
that file.

- The five crates move to the npm side's minors: autostart 2.7.0, deep-link
  2.6.3, dialog 2.8.4, opener 2.7.2, process 2.4.0, all past the 7-day
  cooldown. That drops 61 old crates from Cargo.lock, among them rand 0.7.3,
  one of the open Dependabot alerts, and the unmaintained fxhash.
- package.json and Cargo.toml now state the versions that are actually
  locked, rather than floors several minors below them.
- scripts/check-lockfiles.mjs (npm run check:lockfiles) fails when an
  @tauri-apps package and its crate are on different minors, when
  package-lock.json no longer matches package.json, or when the six places
  that carry the version disagree. With --staged it reads the git index, which
  is how /commit's preflight runs it. The Tests workflow runs it first, in the
  Changelog job, where it takes seconds instead of a release matrix.
- cargo test and clippy run with --locked, so a Cargo.lock that no longer fits
  Cargo.toml fails CI instead of being re-resolved on the runner.

Against the commit before this one, the check reports exactly the five pairs
from the release log plus the stale lockfile version. On this tree it passes,
clippy is clean, 237 Rust tests pass, and a local tauri build gets through the
version check and builds a release binary.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@EarMaster
EarMaster merged commit 43e01d1 into main Nov 11, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant