- notify-ci-failure.yml lists its workflows by name. `workflows: ['*']` is not a wildcard to
workflow_run: it matched nothing, so `main` was red from 2026-09-23 with no one told.
- cargo audit runs a prebuilt cargo-audit (taiki-e/install-action, pinned by commit) with
`--deny warnings`, replacing rustsec/audit-check@v2 - Node 20, a check-run write token, and on a
pull request a failure only for "critical", which is how September's advisories passed every PR.
.cargo/audit.toml's contract (a new informational advisory fails CI) is now what runs.
- security-scan.yml: both audits daily against `main`, so an advisory against something already
merged is reported the day it is published, not at the next PR.
- cargo deny (licences, sources, bans) with deny.toml: the licence allowlist makes "every bundled
licence is GPL-3.0-compatible" a test. The workspace declares `publish = false`, which it never
had - and without which cargo-deny judged the app crates as published ones.
- CodeQL analyses rust and actions as well as javascript-typescript. The comment saying CodeQL had
no Rust support stopped being true in 2025.
- ci-node.yml: Pages and id-token write move from the workflow to the one job that needs them
(Sonar S8233); the audit installs with --ignore-scripts (S6505); a new `tauri lockstep` job
fails when a Tauri crate and its npm package drift apart on Cargo.lock and package-lock.json.
- release.yml: build (read-only token, no persisted credentials) and publish (attest + draft) are
separate jobs; the tag must match all five version fields; SHA256SUMS.txt is LF, which
`sha256sum -c` elsewhere needs; actions/attest-build-provenance attests the .exe and .msi;
softprops/action-gh-release is pinned by commit; `workflow_dispatch` with `dry_run` builds any
ref without attesting or drafting.
- ci-integration.yml also runs for the CLI, exec, audit, release metadata, errors, store, index,
Cargo.lock and rust-toolchain.toml - every one of which its end-to-end steps run through.
- dependabot.yml: cooldowns, a group per ecosystem for Tauri packages and for actions and pip,
TypeScript held below 6.1 (typescript-eslint's peer range), and the rust-toolchain ecosystem.
A multi-ecosystem group would put both Tauri halves in one PR, but what it does to dependencies
outside its patterns is undocumented; the lockstep job covers the gap instead.
- Sonar: NOSONAR with reasons on the dev scripts' argv and PATH lookups; bundle-cli.mjs no longer
claims to run from beforeBuildCommand. The dev CSP moves out of index.html into a Vite plugin
that reads devCsp from tauri.conf.json, so a release build carries one policy, the strict one
(S7039); checked in the dev server, where React Refresh's preamble still runs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first bundle ever built for this project contained exactly one binary. NSIS payload:
`pipdock-app.exe`. MSI `app.cab`: one file. **`pipdock.exe` was not installed at all** — while
PRD P0-12 is "CLI core parity", CLI-SPEC documents the entire surface, `golden.rs` pins 58
snapshots of its output, and the README's own Quick start opens with `pipdock env list`. A
user who installed PipDock had none of it.
Found by listing the installer. `tauri.conf.json` declared no `externalBin` and no
`resources`, so there was nothing to notice in a diff — the config was correct for a
GUI-only app, and nobody had built one to see what came out.
`scripts/bundle-cli.mjs` builds the CLI and stages it as a sidecar under the host triple,
which Tauri strips at bundle time, so it installs as plain `pipdock.exe` beside the GUI. The
triple is asked of `rustc -vV` rather than assumed, since a guess breaks the moment anyone
cross-compiles.
It runs from `beforeBuildCommand`, not only from the release workflow. A locally built
installer and a released one have to be the same artifact; a bundle that differs by who
built it is how "works on my machine" reaches a release. This build proves the clean-checkout
case too — `src-tauri/binaries/` is gitignored and did not exist when the build started.
**`PATH` is deliberately left alone** (owner decision, 2026-08-13). PipDock does not modify
the user's environment, which is the restraint SECURITY §5 already applies to not shipping a
self-updater; the README says where the binary lands and gives the one-liner to add it if
that is what you want.
Verified by rebuilding and listing both installers: NSIS 5.7 → 8.8 MB carrying
`pipdock-app.exe` and `pipdock.exe`; MSI 7.6 → 11.6 MB carrying `Path` and `Bin_pipdock.exe`.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>