docs: describe the release workflow now that it is merged

The architecture guide, AGENTS.md and the threat model said releases were
built by hand or Windows-first; ADR-0009 still listed the release
workflow as future work. The Windows build guide named the missing
Settings > API Keys tab.
This commit is contained in:
shumeiko.it
2026-11-01 02:21:20 +01:00
parent 608c804482
commit 0e2f3197eb
8 changed files with 20 additions and 16 deletions

View File

@@ -149,8 +149,9 @@ npm run dev:server # sidecar on http://localhost:3333, serves the UI from
tsx, Vitest, Vite and the sidecar bundle resolve (P2.1). No `build:packages` is needed
before running or testing; it builds the `dist/` entries for publishing.
- The desktop app (`app/`) has its own dependencies outside the npm workspaces: run
`npm ci` in `app/` once, then `npm run tauri:build:mac:arm64` (or the script for your
platform). It needs a current Rust toolchain. Set `CI=true` when the build runs without
`npm ci` in `app/` once, then `npm run tauri:build:mac:arm64` (or `tauri:build:mac:x64`,
`tauri:build:win`, `tauri:build:linux`). It needs a current Rust toolchain. Releases are
built and smoke-tested on all targets by `.github/workflows/release.yml`. Set `CI=true` when the build runs without
access to Finder, or the DMG step fails while styling the disk image window. The Windows
installer must be built on Windows: see [docs/oss/build-windows.md](docs/oss/build-windows.md).
- The sidecar registers routes for the files in `dist/` when it starts (`@fastify/static`