feat: add the updater public key

This commit is contained in:
tiennm99 committed 2026-10-22 17:32:01 +07:00
1 parent 7e446b6bda
commit 687dd41d47
3 files changed
+8 -7

No files matched your search

+2
View File
@@ -1,3 +1,5 @@
/target
/node_modules
/gen
/usage-monitor.key
/usage-monitor.key.pub
+5 -6
View File
@@ -3,12 +3,11 @@
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.
1. **Finish the updater signing key.** The key pair exists, its public key is
in `tauri.conf.json`, and the `TAURI_SIGNING_PRIVATE_KEY` secret is set.
Still to do: add the `TAURI_SIGNING_PRIVATE_KEY_PASSWORD` secret, and keep
an offline backup of `usage-monitor.key` and its password. Losing either
leaves installed copies unable to 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](plans/reports/code-reviewer-261021-1028-tauri-port-final.md).
+1 -1
View File
@@ -33,7 +33,7 @@
},
"plugins": {
"updater": {
"pubkey": "",
"pubkey": "dW50cnVzdGVkIGNvbW1lbnQ6IG1pbmlzaWduIHB1YmxpYyBrZXk6IDA1RUQyREMxNDdFNTRCMUYKUldRZlMrVkh3UzN0QllncWx6V2I3NC9qOUNQU0tUS211VW1VRTBmLzlLcnl0cnk4UmdXMWY5cWkK",
"endpoints": [
"https://github.com/tiennm99/usage-monitor/releases/latest/download/latest.json"
]