Repository navigation
Update path, proven end to end
This release exists so the updater added in 0.19.3 could be walked through a real
version change instead of asserted.
What was broken before: the plugin was registered and signed, but no UI called
it; the endpoint was a releases/latest/download/latest.json path that returns an
HTML page on GitCode; and latest.json did not exist anywhere. No installed copy
could ever have been offered an update.
Now: Settings → About checks, shows the notes, downloads with a progress bar and
installs after verifying the minisign signature. The browser-served build of the
same UI states it cannot self-update rather than showing a dead button.
Verified
| Step | Evidence |
|---|---|
| Endpoint returns JSON | curl https://gitee.com/badhope/creator-studio/raw/main/latest.json → "version": "0.19.4" |
| Installer at the manifest URL is complete | HTTP 200, 40,555,465 bytes, SHA256 c42bfa2a… matches the local build |
| Signature covers that installer | verified with minisign-verify against the public key compiled into the app: SIGNATURE VALID |
Manifest signature == shipped .sig |
byte-identical |
| Gate | pnpm verify exit 0 · 730 passed · 0 skipped |
Still not automated
Clicking "download and install" inside the packaged WebView2 window needs GUI
automation this environment cannot drive. The network half, the manifest, and the
signature are verified against the real hosts; the in-shell click is covered by
unit tests and by construction, not by an observed run.