Files
pipdock/docs/RELEASE-CI.md
T
poli0981andClaude Opus 5 d829c4f17c feat!: drop the application self-updater
Removes `tauri-plugin-updater` and everything that existed to serve it.

A self-updater is a permanent remote-code-execution path into a tool that already
runs subprocesses against the user's interpreters, and it has to be defended for
the life of the product: a signing key that must never leak, an endpoint that must
never be spoofable, verification logic that must never be bypassable. For something
people open occasionally to tidy an environment, that is a large standing liability
bought for a small convenience.

It was also never actually functional. `plugins.updater.pubkey` has been the literal
string REPLACE_AT_FIRST_RELEASE_WITH_TAURI_SIGNING_PUBLIC_KEY since Phase 0, so the
capability was granted to a plugin that could not verify anything.

What goes:

  - tauri-plugin-updater, its `plugins.updater` config block and endpoint, and the
    `updater:default` capability
  - the release workflow's signing step, `--bundles ...,updater`, and the *.sig /
    latest.json artifact globs
  - TAURI_SIGNING_PRIVATE_KEY and its password from the secrets bootstrap, and the
    keypair generation item from the RELEASE-CI section 5 checklist

Ten crates leave the dependency tree with it: zip, tar, xattr, filetime,
minisign-verify, osakit, objc2-osa-kit, arbitrary, derive_arbitrary and the plugin
itself -- archive extraction, signature verification and AppleScript execution, none
of which PipDock has any other reason to link.

SECURITY section 4 gets simpler as a result: pypi.org is now the *only* host PipDock
connects to. github.com was on that list solely for the updater; the legal gate and
the bug-report deep link hand a URL to the user's browser rather than fetching
anything.

Users move between versions from the GitHub Releases page and verify SHA256SUMS.txt,
which the README already tells them to do because SmartScreen warns on first run.
Recorded in CLAUDE.md as well: Tauri makes adding this back a three-line change, so
the reasoning needs to outlive the commit.

183 tests, fmt and clippy clean, both Tauri JSON files still valid.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-29 22:20:33 +07:00

6.1 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.yml uses a Windows runner — hence ci-rust.yml and release.yml are project-local.
  • reusable-web-react.yml has no working-directory input (it runs npm ci at the repo root — hence package.json lives at the root with Vite's root: './ui', see ARCHITECTURE §2) and no npm audit step, hence the extra local job.
  • reusable-codeql.yml supports 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 audit in ci-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-platform notify.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*)

  1. Windows runner: npm ci && vite build → cargo tauri build --locked producing NSIS .exe + .msi.
  2. Compute and publish SHA256SUMS.txt.
  3. Draft GitHub Release with generated changelog; manual publish (owner review) → announce-release.yml fires the Discord announcement.
  4. 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 LICENSE at 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.yml disabling blank issues.
  • .github/dependabot.yml covering cargo, npm, github-actions and the Code Health pins.
  • rust-toolchain.toml, .nvmrc (24), Cargo.lock/package-lock.json committed.
  • Repo settings (owner, via the GitHub UI or gh — not committable): branch protection on main; 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.