-
Notifications
You must be signed in to change notification settings - Fork 268
feat(win): Abort-path installer rollback with backup retention #3265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Astro-Han
merged 3 commits into
apache:main
from
liugddx:feat/windows-installer-rollback
Aug 23, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P1] Get this step green once and put the log in the PR body before the word "proven" ships. I queried check-runs for every commit on this branch —
90f1a275e,3335af80b,76de157af,db5450d7c,e84ab2c3a,3fc75306d— and thepackagejob is failure, failure, cancelled, failure, failure, failure, with the head's still in progress. Pulling the full logs for the four failed jobs and grepping forverify-windows-installer-rollbackreturns zero hits in every one: the step has never run. The most recent job died in the precedingverify:windows-autoupdateon a CDP attach that took about six minutes against a 90-second budget, which is the very bug the head commit is trying to fix. So the only execution evidence this PR currently has is that a normal 0.1.9→0.1.11 upgrade still passes the lifecycle gate with the hook installed — a happy-path non-regression, not a demonstration of rollback. Until the step reports, "proven" should not appear in the title, indocs/windows-support.md, or in the Chinese docs. When it does run, the body should carry the manifest file count, theexit code 102, the0 differing filesline and the control run. Reproduced by execution against the GitHub API and the job logs.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
transactionalandprovenclaims have been removed from the title, installer/workflow/builder comments, verifier diagnostics, and EN/zh rollback documentation. Exact-head Windows evidence is intentionally still marked pending in the PR body. FreshRelease Windows checkrun 32477989412 is running now; I am leaving this verification thread open until its rollback step completes and the exact log evidence is posted.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fresh exact-head evidence is now green: Release Windows check 32477989412 passed in 23m21s on
68520adc.The rollback step executed after the successful
0.1.11 -> 0.1.12autoupdate and reported:manifest covers 607 files0 differing files across 607 entriesMaka.exerefusal passedverified Abort-path rollback and its boundaries for 0.1.11 -> 0.1.12The PR body now links this run. The old
transactional/provenwording remains removed.