Skip to content

build(deps): tauri-build 2.7 puts the sidecar where Rust 1.100 builds, so the Mac checks pass again - #97

Merged
rgdevment merged 1 commit into
mainfrom
build/tauri-build-for-rust-1-100
Nov 16, 2026
Merged

rgdevment merged 1 commit into
mainfrom
build/tauri-build-for-rust-1-100

Conversation

@rgdevment

Copy link
Copy Markdown
Owner

Context

Rust 1.100 puts a build script's OUT_DIR one folder deeper than before. tauri-build 2.6.3 finds the target folder by going three levels up from it, so it now lands in target/debug/build and copies the sidecar there. On macOS a folder of that name is already there, the build folder of the linkunbound-shell package itself, and removing it as a file fails with "Operation not permitted": every macOS build stops in the build script of linkunbound-settings. It showed first in the macOS test job of #96, at cargo clippy; the release builds on stable too. On Windows the .exe in the name avoids the clash, and the sidecar still lands in the wrong folder.

tauri-build 2.7.0 walks up from OUT_DIR to the build folder instead of counting levels. This moves the lockfile to 2.7.4.

Reading order

  1. Cargo.lock: tauri-build 2.6.3 to 2.7.4 and, with it, tauri-utils 2.9.3 to 2.10.3 and urlpattern 0.3 to 0.6; about 30 packages move in all. tauri itself stays at 2.11.6.
  2. THIRD-PARTY-BUNDLED.md, THIRD-PARTY-LICENSES.md: written again from the new lockfile by npm run notices.

Decisions

Decision Discarded alternative Reason
Move tauri-build to 2.7 Hold CI on Rust 1.99.1 The release builds on stable as well, and a Mac with Rust 1.100 cannot build the app at all until this moves
2.7.4 2.7.5, the newest It is the version Tisty and CopyPaste already build with
tauri stays at ~2.11 Move it to 2.12 with the rest Cargo.toml holds it there: 2.12 brings muda 0.20 while slint stays on 0.19, and two muda break the macOS link

Notes for reviewers

tauri 2.11.6 beside tauri-utils 2.10.3 is a pairing no repository here has run: Tisty and CopyPaste pair tauri 2.12.5 with tauri-utils 2.10.2. tauri-utils ships inside the app, and this branch builds no installer on its own (packaging=false), so the steps below are worth taking before the merge.

How to test

  1. Run the Bundle workflow by hand on this branch → the Windows installer and the macOS bundle build.
  2. Install one of them and open LinkUnbound → the settings window opens.
  3. Open a link from another app → the picker shows and the chosen browser opens it.

Checklist

  • cargo deny check bans licenses sources: bans ok, licenses ok, sources ok
  • npm run notices: 11 packages and 363 crates, both files written again
  • No crate in the new tree declares a rust-version above the repository's 1.97 (cargo metadata --locked)
  • bash scripts/touched.sh answers rust=true, so the Windows and macOS test jobs run on this pull request
  • The macOS test job passes here; on main's tree it fails with Rust 1.100, as in ci: the Dev Drive is mounted beside the checkout, so the Rust cache on Windows keeps its target #96
  • Bundle, run by hand on this branch, builds both
  • After merge: open the app once on Windows and on macOS

@rgdevment
rgdevment merged commit d7a54b1 into main Nov 16, 2026
29 checks passed
@rgdevment
rgdevment deleted the build/tauri-build-for-rust-1-100 branch November 16, 2026 22:43
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