Description
The local-mode resolver explicitly selects linux-arm64 and win32-arm64 binaries, and the upstream server release publishes both assets, but the Python wheel publishing matrix does not build wheels for either platform.
The current server-v3 v3.7.4 release contains:
stagehand-server-v3-linux-arm64stagehand-server-v3-win32-arm64.exe
However, .github/workflows/publish-pypi.yml only publishes Linux x64, macOS arm64/x64, and Windows x64 wheels.
Reproduction / code references
- Inspect
src/stagehand/_custom/sea_binary.py:14-23: aarch64 / arm64 maps to an arm64 packaged filename.
- Inspect
.github/workflows/publish-pypi.yml:17-34: there is no Linux arm64 or Windows arm64 matrix entry.
- Install
stagehand on Linux aarch64 or Windows ARM64 and start local mode without manually setting STAGEHAND_SEA_BINARY.
The source-development documentation also lists Linux and Windows ARM64 binaries in CONTRIBUTING.md, confirming that the server assets are intended to be supported.
Expected behavior
PyPI should offer platform wheels containing stagehand-linux-arm64 and stagehand-win32-arm64.exe, matching the resolver's supported architecture names.
Actual behavior
Those architectures have no matching local-mode wheel. Installation may fall back to an sdist/generic build without a packaged SEA binary, and local startup then fails with FileNotFoundError unless the user manually downloads and configures the binary.
Why this matters
Remote API calls are architecture-independent, so installation can appear successful while the advertised local mode fails only at runtime. The upstream release assets already exist; the Python packaging matrix is the missing link.
Prior-art check
I searched open/closed issues and PRs for ARM64/aarch64 wheels and binary packaging. PRs #260 and #277 adjusted existing binary names/platforms but did not add these two wheel targets, and no issue tracks the missing wheels.
Description
The local-mode resolver explicitly selects
linux-arm64andwin32-arm64binaries, and the upstream server release publishes both assets, but the Python wheel publishing matrix does not build wheels for either platform.The current server-v3 v3.7.4 release contains:
stagehand-server-v3-linux-arm64stagehand-server-v3-win32-arm64.exeHowever,
.github/workflows/publish-pypi.ymlonly publishes Linux x64, macOS arm64/x64, and Windows x64 wheels.Reproduction / code references
src/stagehand/_custom/sea_binary.py:14-23:aarch64/arm64maps to anarm64packaged filename..github/workflows/publish-pypi.yml:17-34: there is no Linux arm64 or Windows arm64 matrix entry.stagehandon Linux aarch64 or Windows ARM64 and start local mode without manually settingSTAGEHAND_SEA_BINARY.The source-development documentation also lists Linux and Windows ARM64 binaries in
CONTRIBUTING.md, confirming that the server assets are intended to be supported.Expected behavior
PyPI should offer platform wheels containing
stagehand-linux-arm64andstagehand-win32-arm64.exe, matching the resolver's supported architecture names.Actual behavior
Those architectures have no matching local-mode wheel. Installation may fall back to an sdist/generic build without a packaged SEA binary, and local startup then fails with
FileNotFoundErrorunless the user manually downloads and configures the binary.Why this matters
Remote API calls are architecture-independent, so installation can appear successful while the advertised local mode fails only at runtime. The upstream release assets already exist; the Python packaging matrix is the missing link.
Prior-art check
I searched open/closed issues and PRs for ARM64/aarch64 wheels and binary packaging. PRs #260 and #277 adjusted existing binary names/platforms but did not add these two wheel targets, and no issue tracks the missing wheels.