CI caught two things the previous commits broke, and the first is pointed: I declared the CLI sidecar in `tauri.conf.json`, and **`tauri-build` validates `externalBin` at build-script time** — so plain `cargo clippy` and `cargo test` on `pipdock-app` began failing in a fresh clone with *"resource path `binaries\pipdock-x86_64-pc-windows-msvc.exe` doesn't exist"*. It passed locally only because I had already staged the file. That is exactly the "works on my machine" failure the commit that introduced it claimed to be preventing. `externalBin` moves to `src-tauri/tauri.bundle.conf.json`, merged with `--config` only when bundling. Compiling the app does not need the sidecar; bundling it does, and the config now says so. Verified the way it should have been the first time: **`src-tauri/binaries/` deleted**, then `cargo clippy -p pipdock-app --all-targets` and `cargo test --workspace` both clean — and `npm run bundle` from that same state stages the sidecar and produces two installers, the NSIS payload still carrying `pipdock-app.exe` and `pipdock.exe`. The whole recipe now lives in one `npm run bundle` script the workflow calls, so nobody has to remember that `--locked` goes after `--` or that the overlay exists. RELEASE-CI §3.1 records both traps rather than just the command. Second breakage: `ci-integration.yml` hardcoded `%LOCALAPPDATA%\PipDock\tools` in three places — it quarantines `ruff.exe` there to prove `PD-HLT-001` — and the data root had moved under `data\`. A test that reaches into a path by hand is a test that has to be told when the path moves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
7 lines
129 B
JSON
7 lines
129 B
JSON
{
|
|
"$schema": "../node_modules/@tauri-apps/cli/config.schema.json",
|
|
"bundle": {
|
|
"externalBin": ["binaries/pipdock"]
|
|
}
|
|
}
|