Fix update install recovery#2308
Open
brennanb2025 wants to merge 1 commit into
Open
Conversation
Co-authored-by: Orca <help@stably.ai>
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
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.
Summary
Testing
I tested this specifically against update-path regression risk, not only generic build health:
pnpm exec vitest run --config config/vitest.config.ts src/main/updater.test.ts src/main/updater.mac-install.test.ts src/main/updater.check-failure.test.ts src/main/update-install-marker.test.ts src/main/update-quit-policy.test.ts src/main/mac-update-relaunch-guard.test.tsquitAndInstall, preparing/installing/restarting marker transitions, marker write failure recovery, recovery retry attempt reuse, completed-update marker cleanup, macOS Squirrel readiness deferral, deferred quit resume, active ShipIt stale relaunch self-quit, stale ShipIt state rejection, duplicate bundle rejection, and normal quit policy behavior.pnpm exec vitest run --config config/vitest.config.ts src/renderer/src/components/UpdateCard.test.ts src/renderer/src/hooks/useIpcEvents.test.ts src/main/updater-nudge.test.tspreparing,installing,restarting, andrecoverystates.pnpm testsrc/renderer/src/components/sidebar/WorktreeCard.quick-actions.test.tsx; rerunning that file alone passed immediately.pnpm run lintDEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer pnpm run build:macdist/orca-macos-x64.dmgdist/orca-macos-arm64.dmgdist/Orca-1.4.6-mac.zipdist/Orca-1.4.6-arm64-mac.zippnpm run build:macattempt failed because the active developer directory was Command Line Tools. Retrying with full Xcode viaDEVELOPER_DIR=/Applications/Xcode.app/Contents/Developersucceeded.Packaged artifact sanity checks:
dist/mac-arm64/Orca.app/Contents/Info.plisthasCFBundleShortVersionString=1.4.6.dist/mac-arm64/Orca.app/Contents/Info.plisthasCFBundleIdentifier=com.stablyai.orca.dist/mac-arm64/Orca.app/Contents/Resources/app-update.ymlexists and points to the GitHub release provider withupdaterCacheDirName: orca-updater.dist/mac-arm64/Orca.app/Contents/Resources/Orca Computer Use.appis packaged.Packaged launch smoke:
dist/mac-arm64/Orca.app/Contents/MacOS/Orcawith a temporaryORCA_USER_DATA_PATH./Applications/Orca.appinstance was already running, so this primarily verified the packaged executable does not crash before Electron single-instance handoff rather than a fully independent fresh-window launch.Risk: high
Historic risk metadata backfill based on the existing
risk:highlabel.