Files

T

502c96630e feat(desktop): Linux AppImage polish — window controls, updater UX, docs (#2144 )

* feat(electron): add Linux AppImage releases

* ci: cache Linux OpenCode CLI artifacts

* fix(ci): await Linux release inventory check

* fix(electron): add frameless window controls on Linux desktop

Linux AppImages were created without native WM decorations and without
in-app controls, leaving users unable to close the window with a mouse.

Treat Linux like Windows: frameless BrowserWindow plus the existing
WindowsWindowControls header buttons and app-menu entry. macOS keeps
hidden title bar with traffic lights unchanged.

Shared usesFramelessElectronChrome() helper drives main window, mini
chat, header insets, and titlebar controls.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* feat(desktop): add configurable window controls position by OS

Add desktopWindowControlsPosition setting (auto/left/right) with OS-aware
defaults: Linux left, Windows right. Wire frameless chrome controls in
Header, TitlebarLeftControls, and MiniChatLayout, plus a Sessions settings
control for Windows and Linux desktop shells.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* fix(desktop): address Linux AppImage release review findings

Propagate updater capability errors to the UI, treat missing
latest-linux.yml feeds as no-update, stop installed-apps IPC spam on
Linux, document FUSE/AppImage limits, add CHANGELOG entry, migrate
remaining btriapitsyn URLs, and run Electron Linux unit tests on PRs.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

---------

Co-authored-by: jibanez-staticduo <staticduo@gmail.com>
Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

2026-07-13 08:59:31 +03:00

1.6 KiB

Raw Blame History

Linux Updater E2E Fixture

This local-only harness verifies AppImage N-to-N+1 replacement without changing the production GitHub updater provider. It supports native x64 and arm64 hosts.

Build both versions on the native target architecture. For N and N+1, set the test-build marker only while bundling main, then complete normal packaging:
```
OPENCHAMBER_TARGET_ARCH=x64 OPENCHAMBER_UPDATER_E2E_BUILD=1 bun run bundle:main
OPENCHAMBER_TARGET_ARCH=x64 node ./scripts/package.mjs --linux --x64 --publish=never
```
Use OPENCHAMBER_TARGET_ARCH=arm64 and --arm64 on an arm64 host. Keep the N and N+1 AppImages in separate output directories before rebuilding.

Launch N against a loopback fixture containing N+1:

bun run updater:e2e:fixture -- run \
  --arch x64 \
  --current /absolute/path/OpenChamber-N-linux-x86_64.AppImage \
  --next /absolute/path/OpenChamber-N+1-linux-x86_64.AppImage \
  --version N+1 \
  --dir /tmp/openchamber-updater-e2e

In N, check for updates, download/install, and restart. Verify the restarted app reports N+1 and that the file at APPIMAGE was replaced. Repeat with --arch arm64 and the arm64 AppImages on the arm64 host.

The harness binds only 127.0.0.1. Runtime override activation additionally requires OPENCHAMBER_E2E=1, the loopback URL set by the harness, and the build-time marker. Normal packages omit the build-time marker and always use openchamber/openchamber. The renderer, IPC bridge, command-line arguments, and persistent configuration do not have access to the feed URL.

1.6 KiB Raw Blame History

Linux Updater E2E Fixture

1.6 KiB

Raw Blame History