Adds an "Update over the running app" step to the Windows smoke workflow. It reproduces what the auto-updater does:
the installed app is running;
the installer starts in passive update mode (/P /UPDATE, as tauri-plugin-updater 2.10 passes);
the app only goes away 3 s later, standing in for a slow shutdown, which is what produced "Error opening file for writing: cinny.exe".
It passes when the installer finishes by itself (no dialog, 90 s cap), exits 0, and has rewritten cinny.exe. Its timestamp is set to 2000 first, and NSIS writes the build's own timestamp back.
Result (run 2797, real windows runner, published nightly with the #1 pre-install hook): installer exit code 0; cinny.exe timestamp now 10/20/2026 21:40:46. The step passed, and every other smoke check passed too (login screen, local server, microphone for the app and not a foreign page, call page on its own origin and isolated, keychain round trip).
This is the real-update confirmation #1 was left open for, so #1 can close. #19 stays open for the parts not covered yet: deep links, global hotkeys, tray commands, and the update-ready path with a mocked feed.
Refs #1 and #19.
Adds an **"Update over the running app"** step to the Windows smoke workflow. It reproduces what the auto-updater does:
- the installed app is running;
- the installer starts in passive update mode (`/P /UPDATE`, as `tauri-plugin-updater` 2.10 passes);
- the app only goes away **3 s later**, standing in for a slow shutdown, which is what produced "Error opening file for writing: cinny.exe".
It passes when the installer finishes by itself (no dialog, 90 s cap), exits 0, and has rewritten `cinny.exe`. Its timestamp is set to 2000 first, and NSIS writes the build's own timestamp back.
**Result** (run 2797, real `windows` runner, published nightly with the #1 pre-install hook): `installer exit code 0; cinny.exe timestamp now 10/20/2026 21:40:46`. The step passed, and every other smoke check passed too (login screen, local server, microphone for the app and not a foreign page, call page on its own origin and isolated, keychain round trip).
This is the real-update confirmation #1 was left open for, so #1 can close. #19 stays open for the parts not covered yet: deep links, global hotkeys, tray commands, and the update-ready path with a mocked feed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
After the smoke test, start the installed app, run the installer in
passive update mode (/P /UPDATE) while it runs, and only stop the app 3 s
later. Passes when the installer finishes by itself (no "Error opening
file for writing" dialog), exits 0, and has rewritten cinny.exe.
Refs #1, #19
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Refs #1 and #19.
Adds an "Update over the running app" step to the Windows smoke workflow. It reproduces what the auto-updater does:
/P /UPDATE, astauri-plugin-updater2.10 passes);It passes when the installer finishes by itself (no dialog, 90 s cap), exits 0, and has rewritten
cinny.exe. Its timestamp is set to 2000 first, and NSIS writes the build's own timestamp back.Result (run 2797, real
windowsrunner, published nightly with the #1 pre-install hook):installer exit code 0; cinny.exe timestamp now 10/20/2026 21:40:46. The step passed, and every other smoke check passed too (login screen, local server, microphone for the app and not a foreign page, call page on its own origin and isolated, keychain round trip).This is the real-update confirmation #1 was left open for, so #1 can close. #19 stays open for the parts not covered yet: deep links, global hotkeys, tray commands, and the update-ready path with a mocked feed.
🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5