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>
6.9 KiB
PipDock — Release & CI
Version 0.2 · 2026-07-27 · CI reuses the poli0981/.github ops repo where a suitable reusable workflow exists, and is project-local where one does not. The ops repo's suite was audited on 2026-07-27 (see §1 note) — do not assume a reusable exists without checking.
1. Workflows (.github/workflows/)
| Workflow | Kind | Triggers | Jobs |
|---|---|---|---|
ci-rust.yml |
project-local | PR, push main | windows-latest: cargo fmt --check, clippy -D warnings, cargo test --locked, cargo audit |
ci-node.yml |
caller → ops reusable-web-react.yml + one local job |
PR, push main | Node 24, npm ci, lint / typecheck / Vitest (each runs only if the npm script exists), vite build; local job adds npm audit --audit-level=high |
ci-integration.yml |
project-local | PR touching engine|plan|snapshot|graph, nightly |
Windows runner, disposable-venv suite (TESTING L2), weekly latest-engine parser job |
codeql.yml |
caller → ops reusable-codeql.yml |
PR, schedule | languages: '["javascript-typescript"]' only |
release.yml |
project-local | tag v* |
windows-latest build, sign, bundle, publish (see §3) |
announce-release.yml |
caller → ops announce-release.yml |
release published | Discord release announcement |
notify-ci-failure.yml |
caller → ops notify-ci-failure.yml |
workflow_run completed |
Discord CI-failure notification |
Ops-repo audit (2026-07-27) — why the table looks like this:
- The reusable suite covers assembly, c-cpp, chrome-extension, desktop-csharp, go, jvm, macos-swift, php, python, r, ruby and web-react. There is no Rust reusable and no Tauri reusable, and only
reusable-desktop-csharp.ymluses a Windows runner — henceci-rust.ymlandrelease.ymlare project-local. reusable-web-react.ymlhas noworking-directoryinput (it runsnpm ciat the repo root — hencepackage.jsonlives at the root with Vite'sroot: './ui', see ARCHITECTURE §2) and nonpm auditstep, hence the extra local job.reusable-codeql.ymlsupports csharp, python, javascript-typescript, ruby, c-cpp, java-kotlin, go and swift. CodeQL has no Rust analyzer, so Rust security coverage comes from clippy-D warnings+cargo auditinci-rust.yml, not from CodeQL.- Portfolio notifications are Discord-only, driven by the ops repo's
.github/scripts/discord_notify.py. There is no multi-platformnotify.py.
Permissions matrix (explicit in every caller — the Phase-5 lesson: callers without a permissions: block default everything to none):
# codeql.yml
permissions: { actions: read, contents: read, security-events: write }
# announce-release.yml / notify-ci-failure.yml
permissions: { contents: read, actions: read }
# release.yml
permissions: { contents: write } # release assets
# ci-*.yml
permissions: { contents: read }
2. Branch & version policy
main protected (PR + green CI required). SemVer; tags vX.Y.Z. Conventional commits feed the changelog generator.
Dependency updates use Dependabot (.github/dependabot.yml) — the portfolio standard, as evidenced by the ops repo's dependabot-summary.yml; there is no Renovate configuration anywhere in the ops repo. Four ecosystems: cargo, npm, github-actions, and pip scoped to tools-requirements.txt (the Code Health pins). Weekly schedule with minor/patch grouped per ecosystem; security advisories arrive as immediate, ungrouped PRs (Dependabot's default for security updates), and the pip ecosystem stays its own group so Code Health pin bumps are reviewable in isolation. Watching pip/uv releases to trigger the parser-fixture job is the scheduled job in ci-integration.yml, not the dependency bot.
3. Release pipeline (tag v*)
-
Windows runner:
npm ci→npm run bundle, producing NSIS.exe+.msi. That one script owns the whole recipe so the workflow cannot drift from what a developer runs locally, and it encodes two things that are easy to get wrong:--lockedgoes after--. It is cargo's flag;tauri buildrejects it as its own with "unexpected argument" before a single crate compiles.- The CLI sidecar is declared in an overlay (
src-tauri/tauri.bundle.conf.json, merged with--config), not intauri.conf.json.tauri-buildvalidatesexternalBinat build-script time, so declaring it in the base config makes plaincargo clippyandcargo testfail in a fresh clone with "resource path … doesn't exist" — a bundling concern leaking into every compile.
The frontend is built by tauri's
beforeBuildCommand, so the workflow does not runvite builditself. -
Compute and publish
SHA256SUMS.txt. -
Draft GitHub Release with generated changelog; manual publish (owner review) →
announce-release.ymlfires the Discord announcement. -
Post-release checklist issue auto-opened: verify SmartScreen behavior, spot-check EN/VI in the shipped build.
There is no signing step. PipDock does not update itself (SECURITY §5), so no latest.json is produced, no artifact is signed, and no keypair exists to manage.
Secrets bootstrap: set per-repo with gh secret set (the ops repo has no setup-secrets.sh) — the Discord webhooks the ops-repo notifiers expect (DISCORD_RELEASES_WEBHOOK, DISCORD_REPO_WEBHOOK, DISCORD_CI_WEBHOOK; the callers pass secrets: inherit). That is the whole list.
4. Artifact & support policy
Two active lines at most: latest release gets features; previous minor gets security-only patches for 90 days. Users move between versions by downloading from the Releases page — there is no update channel to target. MSI provided for org deployment; winget manifest submission is P2 (tracked in ROADMAP), and would be the natural place to add an upgrade path that is not PipDock's own code.
5. Repo scaffolding checklist (day one)
- GPL-3.0
LICENSEat root;legal/committed publicly (the in-app legal gate links to these GitHub URLs — CommandForge lesson: don't leave them gitignored). .github/ISSUE_TEMPLATE/bug_report.yml(shipped in this suite) +config.ymldisabling blank issues..github/dependabot.ymlcovering cargo, npm, github-actions and the Code Health pins.rust-toolchain.toml,.nvmrc(24),Cargo.lock/package-lock.jsoncommitted.- Repo settings (owner, via the GitHub UI or
gh— not committable): branch protection onmain; disable Advanced Security → CodeQL Default setup (the reusable is advanced-setup and is rejected at upload time otherwise); enable Discussions for the issue-template contact links. - Secrets via
gh secret set: the Discord webhooks (DISCORD_RELEASES_WEBHOOK,DISCORD_REPO_WEBHOOK,DISCORD_CI_WEBHOOK). No signing key — see §3. - Replace the placeholder app icon (
src-tauri/icons/) in the ROADMAP Phase 3 branding pass. - README badges: CI, CodeQL, release, license.