Rename server package to server-v3
MO
8mo ago+27+27+01234567890123456789-3-3-0123456789
why
Nick's PR had both some server-v3 changes and server-v4 changes. I split it into two prs - just the v3 changes here, and just the v4 changes here (WIP).
Then, once I rebased this PR, it's really just one small change to the node SEA binary stuff.
test plan
Verified the split with exact file manifests before creating the branch and ran pnpm install --lockfile-only --ignore-scripts.
Summary by cubic
Renamed the Stagehand server to packages/server-v3 and @browserbasehq/stagehand-server-v3. Updated CI, release, tests, and scripts to use the new paths and SEA binary names, and hardened the SEA build. No API or runtime changes.
-
Refactors
- Moved
packages/servertopackages/server-v3and renamed the package to@browserbasehq/stagehand-server-v3. - Updated GitHub workflows (CI, SEA build, release) and artifacts to
stagehand-server-v3-*. - Switched OpenAPI/Stainless references to
packages/server-v3/openapi.v3.yaml. - Updated test discovery/commands and Turbo tasks to target
@browserbasehq/stagehand-server-v3; adjusted ESLint, workspace, and scripts accordingly. - Hardened SEA build: verify Node binary includes the required fuse, fall back to the official Node distro when needed, enforce fuse presence, use
stagehand-server-v3-seatemp paths, and centralize the fuse value.
- Moved
-
Migration
- Use
@browserbasehq/stagehand-server-v3inpnpm/Turbo filters and scripts. - Run local tasks from
packages/server-v3. - For SEA builds/tests, use binaries named
stagehand-server-v3-<platform>-<arch>and setSEA_BINARY_NAMEif needed.
- Use