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:
@@ -44,6 +44,7 @@ The project owner chose this over publishing the server to npm on 2026-11-01.
|
||||
tests.
|
||||
- An archive is about 130 MB (macOS arm64); it is downloaded once per version.
|
||||
- `install.sh`, `scripts/waggle-server.sh` and their CI job are removed.
|
||||
- The release workflow must build the archive on each target system (P1.3d).
|
||||
- The release workflow (`release.yml`) builds the archive on each target system and
|
||||
smoke-tests the installer against it.
|
||||
- Windows cannot replace a running program: `update` and `uninstall` there run through `npx`,
|
||||
and the server must be stopped first.
|
||||
|
||||
@@ -25,7 +25,7 @@ work packages wait for the answer.
|
||||
|---|---|---|
|
||||
| Licensing review (includes code copied from the Apache-2.0 `hive-mind-core` into MIT `core`, ADR-0007) | Technical license checks continue | P2.3, P2.6 |
|
||||
| Product name and system identifiers | Temporary names | P1.3d, P2.6 |
|
||||
| Location of the public repository | Manual builds on each OS | P1.3d, P2.6 |
|
||||
| Location of the public repository | `release.yml` is ready but has not run; the installer has no default download location (`--from`) | P2.6, P2.7 |
|
||||
| Supported platforms for v1 | Windows x64, macOS arm64 and x64, Linux x64 (glibc) | P1.3b, P1.3d |
|
||||
| Installer signing | First release may ship unsigned with launch instructions | P2.5 |
|
||||
| Separate data directory from the commercial edition | Not separated yet | P1.3c |
|
||||
|
||||
@@ -114,7 +114,7 @@ node scripts/release-smoke.mjs desktop --app "$env:LOCALAPPDATA\Waggle\waggle.ex
|
||||
Home screen.
|
||||
3. If it stays on "Starting Waggle…", close it and take the log from
|
||||
`%USERPROFILE%\.waggle\logs\service.log`.
|
||||
4. Chat needs a model: an API key in Settings → API Keys, or a running Ollama.
|
||||
4. Chat needs a model: an API key in Settings → Models (Provider Keys), or a running Ollama.
|
||||
|
||||
Waggle keeps its data in `%USERPROFILE%\.waggle`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user