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:
@@ -185,14 +185,16 @@ payload and `apps/web/dist` into the server archive for that target, with a `.sh
|
||||
```bash
|
||||
npm ci
|
||||
(cd app && npm ci)
|
||||
(cd app && npm run tauri:build:mac:arm64) # or tauri:build:mac:x64, tauri:build:win, tauri:build
|
||||
(cd app && npm run tauri:build:mac:arm64) # or tauri:build:mac:x64, tauri:build:win, tauri:build:linux
|
||||
npm run build:server-archive # set TARGET_ARCH=x64 after an x64 macOS build
|
||||
```
|
||||
|
||||
The Windows build must run on Windows; see [docs/oss/build-windows.md](oss/build-windows.md).
|
||||
The first community release is unsigned ([docs/oss/signing.md](oss/signing.md)). The release
|
||||
workflow for the community edition is not set up yet, so releases are built by hand on each
|
||||
system.
|
||||
Releases are built by `.github/workflows/release.yml`. On each target (Windows x64, macOS
|
||||
arm64 and x64, Linux x64) it stages the sidecar, packs the server archive, builds the Tauri
|
||||
bundles and smoke-tests both the server installer and the installed desktop app. A `v*` tag
|
||||
creates a draft GitHub release with a `SHA256SUMS` file. The first community release is
|
||||
unsigned, apart from an ad-hoc signature on macOS ([docs/oss/signing.md](oss/signing.md)).
|
||||
|
||||
Shipped dependencies are checked for licenses that allow MIT distribution
|
||||
(`npm run check:licenses`, and `cargo deny` for the Rust crates), and their notices are in
|
||||
|
||||
Reference in New Issue
Block a user