Files
claude-code-usage-bubble/TODO.md
T
tiennm99 6afd603d5e refactor: rename the project to usage-monitor
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.
2026-10-22 16:59:32 +07:00

1.1 KiB

TODO

Steps left before the Tauri v2 port on feat/tauri-port can ship. Do them in order.

  1. Create the updater signing key. Run npx tauri signer generate, put the public key in plugins.updater.pubkey in tauri.conf.json, add the TAURI_SIGNING_PRIVATE_KEY and TAURI_SIGNING_PRIVATE_KEY_PASSWORD repository 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.
  2. Test on Windows 10 and 11. Download the exe artifact from the latest CI run on feat/tauri-port and work through the checklist in the final port review. Check toast notifications first: a freshly downloaded exe may not show them.
  3. Run the release dry run. Follow the dry-run steps in docs/release-process.md. It creates a draft release and deletes it afterwards.
  4. Merge into main. This reaches production: the next tag publishes the Tauri build to existing users through self-update.