You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/design/desktop-electron-to-tauri-update-bridge.md
+10-54Lines changed: 10 additions & 54 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,65 +2,21 @@
2
2
3
3
## Context
4
4
5
-
The last published desktop release, `desktop-v0.0.5`, is an Electron app named `Qwen Code Desktop` with bundle identifier `com.alibaba.qwen-code`. Its macOS updater reads `latest-mac.yml` from the fixed `desktop-latest` release and installs a ZIP archive.
6
-
7
-
The new desktop shell is a Tauri app. It currently uses a different product name and bundle identifier and publishes `desktop-latest.json`, so the existing Electron app cannot discover or replace it.
8
-
9
-
## Goals
10
-
11
-
- Let signed macOS Electron `0.0.5` installations update directly to the first stable Tauri release.
12
-
- Preserve the existing macOS application identity so the updater replaces the installed app bundle.
13
-
- Keep Tauri's signed updater feed for all releases after the migration.
14
-
- Make the bridge opt-in and one-time; later releases must not need Electron build tooling.
15
-
16
-
## Non-goals
17
-
18
-
- Migrating Electron settings, sessions, or workspace state. The Tauri app may ask for a workspace on first launch.
19
-
- Bridging Windows or Linux Electron installations.
20
-
- Generating Electron differential blockmaps. Electron updater falls back to the checksum-verified full ZIP.
5
+
OpenWork Electron releases use GitHub's latest stable release and read `latest-mac.yml`, `latest.yml`, or `latest-linux.yml`. Tauri reads `latest.json` from the fixed `desktop-latest` release. A stable Tauri release must therefore publish both update formats, and the versioned release must remain GitHub Latest for legacy clients.
21
6
22
7
## Compatibility contract
23
8
24
-
The Tauri bundle uses the legacy macOS identity:
25
-
26
-
- product name: `Qwen Code Desktop`
27
-
- bundle identifier: `com.alibaba.qwen-code`
28
-
- artifact prefix: `Qwen-Code-Desktop`
29
-
- signing identity: the existing Developer ID Application certificate
30
-
31
-
The bridge release must be newer than `0.0.5`. It publishes two updater views over the same signed app bundles:
32
-
33
-
1.`latest-mac.yml` points legacy Electron clients at `Qwen-Code-Desktop-arm64.zip` or `Qwen-Code-Desktop-x64.zip`.
34
-
2.`desktop-latest.json` points Tauri clients at the signed Tauri updater archives.
35
-
36
-
The ZIP is created from the already signed and notarized `.app`; it is not rebuilt by Electron tooling.
37
-
38
-
## Release flow
39
-
40
-
`Desktop Release` gains an `electron_bridge` input, disabled by default.
41
-
42
-
- All macOS builds continue to produce the Tauri app, DMG, updater archive, and updater signature.
43
-
- When `electron_bridge` is enabled, each macOS build also creates a legacy-compatible ZIP.
44
-
- The publish job generates `latest-mac.yml` from the two ZIPs and two DMGs.
45
-
- A stable bridge release uploads the legacy metadata and payloads to `desktop-latest` together with `desktop-latest.json`.
46
-
- Later stable releases leave `electron_bridge` disabled. Updating `desktop-latest.json` does not remove the bridge files, so Electron installations that return later can still cross to Tauri.
47
-
48
-
Draft and prerelease runs may build and publish bridge artifacts for inspection, but they never update the stable feed.
49
-
50
-
## Signing credentials
51
-
52
-
The repository already stores the Electron-era Apple certificate and App Store Connect API key under `MAC_CSC_*` and `APPLE_NOTARY_*` secret names. The workflow accepts those names as fallbacks for the newer Tauri names, so the Developer ID identity remains unchanged.
9
+
OpenWork 0.2.0 keeps the Electron product name `OpenWork` and application identifier `com.alibaba.openwork`. With `electron_bridge` enabled, a release contains:
53
10
54
-
Tauri updater artifacts additionally require `TAURI_SIGNING_PRIVATE_KEY`; `TAURI_SIGNING_PRIVATE_KEY_PASSWORD` is only needed for an encrypted private key. The private key must match the public key in the Tauri configuration before the first published Tauri release.
11
+
-`latest-mac.yml` plus versioned ZIP and DMG payloads for Apple Silicon and Intel;
12
+
-`latest.yml` plus the x64 NSIS installer for Windows;
13
+
-`latest-linux.yml` plus the x64 AppImage for Linux;
14
+
-`latest.json` and signed updater archives for Tauri clients.
55
15
56
-
## Validation
16
+
The macOS ZIPs are created from the signed and notarized Tauri app. Windows removes the matching per-user Electron installation through its registered uninstaller before Tauri writes files, preserving user data and avoiding duplicate uninstall entries. Linux AppImage updates replace the current AppImage directly.
57
17
58
-
Automated release-helper tests verify:
18
+
## Release usage
59
19
60
-
- the legacy application identity,
61
-
- exact bridge artifact selection,
62
-
- SHA-512 and size values in `latest-mac.yml`,
63
-
- failure when a required bridge artifact is missing,
64
-
- existing Tauri updater manifest and version synchronization behavior.
20
+
`Desktop Release` defaults `electron_bridge` to true. For a stable release, use `dry_run=false`, `draft=false`, and `prerelease=false`. A stable bridge release is marked GitHub Latest and updates the fixed Tauri feed. Keep the bridge enabled on later stable releases while Electron installations remain supported. Once support is intentionally retired, disable it; later Tauri-only releases use `--latest=false`, so the previous bridge release remains GitHub Latest for dormant Electron clients.
65
21
66
-
Before the stable release, install the signed `desktop-v0.0.5` arm64 and x64 builds, point them at an isolated bridge feed, and verify both `0.0.5 -> Tauri bridge` and `Tauri bridge -> newer Tauri` updates.
22
+
Before publishing, verify signed 0.1.4 clients on each platform can install the bridge and that the resulting Tauri app can then update to a newer Tauri release. Retire the bridge only after the legacy support window is explicitly closed.
0 commit comments