electrobun-release

# Electrobun Release Publishing an Electrobun app means hosting a static set of artifacts and pointing the app's `baseUrl` at them. The Updater polls `update.json`, downloads the tarball or a binary patch, and replaces the running app. --- ## Release Channels | Channel | Built with | Updates | Codesign | |---------|-----------|---------|---------| | `stable` | `--env=stable` | Yes | Required | | `canary` | `--env=canary` | Yes | Required | | `dev` | `electrobun dev` | Disabled | Skipped | Each channel is independent: a user can have `MyApp` (stable) and `MyApp-canary` (canary) installed side-by-side. App data lives in separate directories per channel: - macOS: `~/Library/Application Support/{identifier}/{channel}/` - Windows: `%LOCALAPPDATA%/{identifier}/{channel}/` - Linux: `~/.local/share/{identifier}/{channel}/` --- ## Configuration ```typescript // electrobun.config.ts export default defineConfig({ release: { baseUrl: "https://updates.example.com/", // required for updates generatePatch: true, // default: true } }); ``` `baseUrl` is embedded in `version.json` at build time. The Updater reads it at runtime to construct all update URLs. Without `baseUrl`, updates are silently disabled. --- ## Artifact Naming All remote artifacts follow `{channel}-{os}-{arch}-{filename}`. OS strings: `macos` / `win` / `linux` ### Update Manifest ``` {channel}-{os}-{arch}-update.json Examples: stable-macos-arm64-update.json s...