[Feat] Prepare HoloDesktop for native Windows ARM64 - #8
Open
h-kaiy wants to merge 9 commits into
Open
Conversation
h-kaiy
commented
Jul 15, 2026
| @@ -0,0 +1 @@ | |||
| windows-arm64=0000000000000000000000000000000000000000000000000000000000000000 | |||
h-kaiy
commented
Jul 15, 2026
| # Placeholder digest (bump_runtime.py needs a hex literal anchor); the release pipeline fills it in. | ||
| "windows-arm64": _artifact( | ||
| "hai-agent-runtime-windows-arm64.zip", | ||
| "0000000000000000000000000000000000000000000000000000000000000000", |
h-kaiy
marked this pull request as ready for review
July 15, 2026 09:21
…nd a friendly unavailable error Windows ARM64 users previously hit a bare RuntimeError; every unpublished platform (absent or placeholder) now raises RuntimeArtifactUnavailable with the PATH / download-env-override guidance. The placeholder entry makes the next runtime release require a windows-arm64 sha, so client and pipeline ship together. Co-authored-by: Cursor <cursoragent@cursor.com>
cm2435-hcomp
force-pushed
the
kai/windows-arm64-runtime
branch
from
July 23, 2026 09:10
4919556 to
5da6f1f
Compare
cm2435-hcomp
changed the title
cm2435-hcomp
approved these changes
Jul 27, 2026
* Spike Windows ARM64 desktop readiness * Route readiness spike through full E2E workflow * Close hosted Windows first-run surfaces * Require Windows OOBE broker to exit * Probe rendered Windows privacy experience * Remove Windows readiness spike routing * ci: complete Windows ARM privacy OOBE before e2e * ci: walk Windows privacy OOBE to completion * ci: click through hosted Windows privacy OOBE * ci: gate Windows privacy state on visible UI * ci: allow an idle Windows desktop without foreground * ci: prepare Windows desktop immediately before e2e * style: format Windows readiness workflow test * ci: isolate Windows ARM64 installer smoke
abonneth
approved these changes
Jul 27, 2026
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
3 participants
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.
Why
HoloDesktop detects native Windows ARM64 as
windows-arm64, but the managed runtime, installer, CI, and qualification workflows previously covered only Windows x86_64. Users therefore received a generic missing-artifact failure, and the release pipeline had no contract requiring the ARM64 binary to ship with the client.What
windows-arm64managed-runtime entry and SHA sidecar. The next runtime pin bump must replace it with a real digest.RuntimeArtifactUnavailablepath.install.ps1to distinguish X64 from Arm64 using the qualifiedRuntimeInformationtype.cryptographyagainst a current static OpenSSL in native ARM CI. Upstream stopped publishing Windows ARM64 wheels after 46.0.3; pinning that wheel would embed a vulnerable pre-security-update OpenSSL.windows-11-armunit and fresh-installer CI. Before the runtime is published, the installer job validates the CLI path while deliberately skipping runtime bootstrap; after the real SHA lands, the same job exercises the managed runtime.windows-arm64full-E2E selector while keeping it out of theallrelease matrix until the real runtime is pinned.install.hcompany.ai.Ship-together contract
Companion runtime PR: hcompai/hai#12375.
Merge this client scaffold before cutting the next
runtime/v*tag. The HAI release workflow will then publish the Windows ARM64 artifact and open a pin-bump PR containing all four platform digests. Do not cut a HoloDesktopv*release from this placeholder state.The Holo distribution release also needs to publish a current Windows ARM64
cryptographywheel (or adopt an equivalent supported binary dependency path). CI can build it from source because the hosted image has MSVC, Rust, and vcpkg; a clean customer machine cannot be required to have that toolchain.Validation
uv run ruff format --check .uv run ruff check .uv run mypy src/uv run pytest -q(442 passed, 16 skipped)actionlint .github/workflows/*.ymlpython find --managed-pythonuv-aarch64-pc-windows-msvc.zipSHA verified from the uv 0.9.18 releasePromotion state
cryptographybinary dependency: pending the Holo distribution release.