Repository navigation
fix(ci): prevent MSI Restart Manager from closing the Windows runner - #1213
Merged
Merged
Conversation
Collaborator
Author
|
Reviewed CI-only policy set/restore, retained both installer/IME smoke checks and unchanged packaging/source guards. Local contract checks and exact-head cloud CI 38888000367 are green (7/7). Authorized administrator fast-forward keeps tested tooling commit; no branch protections changed. Next dispatch is Windows-only against immutable new Stable v2.0.1-tauri draft. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two Stable build attempts deterministically stop ~1s into MSI install with runner shutdown, after successful NSIS/IME smoke and MSI generation. Temporarily disable Windows Installer Restart Manager interaction on the disposable CI host via documented per-machine policy; restore it in finally. Both actual NSIS/MSI installation, uninstall and COM/TSF checks remain mandatory. No production/application/version/tag changes. Contract checks ordering, restoration and preserved smoke failures; local MSI and publication contracts pass. After exact-head CI, use existing admin/draft/tag-source guarded Windows-only repair on v2.0.1-tauri, not old 2.0.0; preserve successful macOS/Android assets. Evidence: docs/releases/2.0.1-windows-ci-isolation-20261016.md.