mirror of
https://github.com/tiennm99/claude-code-usage-bubble.git
synced 2026-10-25 08:17:37 +00:00
Rename the crate, binary, product name, identifier, settings folder, log file, autostart entry, user agent, updater endpoint and release assets. Legacy Win32 clients still update: they fall back to the first .exe asset, and the legacy rollback workflow reads the package name from the ref it builds. Upgraded installs start with default settings.
1.1 KiB
1.1 KiB
TODO
Steps left before the Tauri v2 port on feat/tauri-port can ship. Do them in
order.
- Create the updater signing key. Run
npx tauri signer generate, put the public key inplugins.updater.pubkeyintauri.conf.json, add theTAURI_SIGNING_PRIVATE_KEYandTAURI_SIGNING_PRIVATE_KEY_PASSWORDrepository secrets, and keep an offline backup of the key pair. Until then the release workflow refuses to build and the app rejects every downloaded update. - Test on Windows 10 and 11. Download the exe artifact from the latest CI
run on
feat/tauri-portand work through the checklist in the final port review. Check toast notifications first: a freshly downloaded exe may not show them. - Run the release dry run. Follow the dry-run steps in docs/release-process.md. It creates a draft release and deletes it afterwards.
- Merge into
main. This reaches production: the next tag publishes the Tauri build to existing users through self-update.