70 行
4.1 KiB
Markdown
70 行
4.1 KiB
Markdown
# P00-08: Build, CI, and Release Readiness
|
|
|
|
- Status: Local Windows build passed; Forgejo CI, signing, and updater release configuration remain pending
|
|
- Date recorded: 2026-07-18
|
|
- MVP gate: Required before declaring P00 complete
|
|
|
|
## Objective
|
|
|
|
Verify reproducible frontend, Rust, Tauri development, Windows production-build, Forgejo CI, installer, updater, and signing prerequisites without creating temporary release credentials or claiming unexecuted jobs passed.
|
|
|
|
## Environment
|
|
|
|
- Node.js: 24.17.0 detected
|
|
- pnpm: 11.9.0 detected
|
|
- Rust/Cargo: 1.97.1 detected and verified
|
|
- MSVC C++ build tools: verified by debug and release links
|
|
- WebView2: previously detected
|
|
- Forgejo SSH endpoint: connection refused at localhost:18086
|
|
- Forgejo runner labels: unknown
|
|
- Windows code-signing certificate: not configured
|
|
- Tauri updater signing key and endpoint: not configured
|
|
|
|
## Minimal validation implementation
|
|
|
|
The repository pins Node, pnpm, Rust, direct JavaScript dependencies, and lockfiles. Local scripts cover frontend and Rust checks. Forgejo CI provides:
|
|
|
|
- A portable Linux quality job for frontend, workspace, and Rust checks.
|
|
- A Windows Tauri job guarded by the ENABLE_WINDOWS_TAURI_CI repository variable.
|
|
- No publication, release upload, or long-lived secret use.
|
|
|
|
## Required execution
|
|
|
|
1. Install dependencies from committed lockfiles.
|
|
2. Run frontend format, lint, typecheck, unit tests, and production build.
|
|
3. Run Rust fmt, Clippy with warnings denied, tests, and check.
|
|
4. Start Tauri development mode on Windows and verify IPC plus tray hide/restore.
|
|
5. Run the Windows Tauri production build.
|
|
6. Inspect Forgejo runner labels and enable only jobs with verified prerequisites.
|
|
7. Run the Forgejo workflow and retain sanitized results.
|
|
8. Record installer bundle prerequisites.
|
|
9. Record code-signing and updater requirements without generating temporary production keys.
|
|
|
|
## Actual execution result
|
|
|
|
Local Windows validation passed: frontend format/lint/type/unit/build checks, Playwright Chrome smoke, Rust fmt/check/Clippy/tests, Tauri development launch, release executable build, and NSIS bundle generation all completed successfully.
|
|
|
|
The first two bundle attempts timed out while Tauri downloaded its official NSIS archive. The official tauri-bundler 2.9.4 source confirmed the standard cache path and embedded SHA-1 values. The NSIS 3.11 archive and nsis-tauri-utils 0.5.3 DLL were then downloaded from their official Tauri release URLs, matched the embedded SHA-1 values, installed into the standard cache, and the bundle succeeded.
|
|
|
|
Installer: `AstrBot Desktop_0.1.0-alpha.0_x64-setup.exe`, 3,552,257 bytes, SHA-256 `BF87DCD13B81C18EFC9A2DB8DE6E201396FFBB9ABA0EABC579A22479C004816C`.
|
|
|
|
Forgejo API confirmed the repository existed and was empty before initialization. Git Credential Manager reauthentication then enabled a normal, non-forced HTTP push of `main` at `0d12b94`, and `feat/p00-bootstrap` was created from that baseline. The configured SSH origin `localhost:18086` still refuses connections; the LAN SSH endpoint responds but rejects the available key. The workflow file has not run, and the action-runner jobs endpoint returned 404, so no CI success is claimed.
|
|
|
|
## Log summary
|
|
|
|
Local command logs support the Windows build claims. No Forgejo workflow, code-signing, updater-signing, or publication result exists.
|
|
|
|
## Known limitations
|
|
|
|
- The ubuntu-latest and windows-latest labels are assumptions until a Forgejo act_runner is inspected.
|
|
- Linux checks cannot certify Windows Credential Manager, UI Automation, Event Log, window capture, UNC behavior, tray behavior, or Windows bundling.
|
|
- Action availability and outbound registry access are unknown.
|
|
- Code signing and updater verification remain release-stage work.
|
|
|
|
## Security impact
|
|
|
|
CI must not receive AstrBot, NAS, SSH, signing, or updater secrets during P00. Action references should be pinned to reviewed commit hashes after runner connectivity is restored.
|
|
|
|
## Recommendation
|
|
|
|
Treat Windows local checks as mandatory until a trusted Windows runner is configured. Mark the Windows job skipped when the enabling variable is absent, and never interpret that skip as a successful Windows build.
|