Open SourceAutomated release watch

stagehand-python@4.2.0a0.dev1587: Point eval sites at Vercel instead of GitHub Pages ( 3141)

Browserbase Stagehand releases published stagehand-python@4.2.0a0.dev1587: Point eval sites at Vercel instead of GitHub Pages ( 3141). GitHub Pages has been unreliable for the eval sites, so they now also deploy to Vercel at https://stagehand-eval-sites.vercel.app/ . This PR swaps the host. Paths are unchanged:…

Human read

Why this signal matters

Browserbase Stagehand releases published stagehand-python@4.2.0a0.dev1587: Point eval sites at Vercel instead of GitHub Pages ( 3141). This automated release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: GitHub Pages has been unreliable for the eval sites, so they now also deploy to Vercel at https://stagehand-eval-sites.vercel.app/ . This PR swaps the host. Paths are unchanged: https://browserbase.github.io/stagehand-eval-sites/sites/ /… https://stagehand-eval-sites.vercel.app/sites/ /… What changed (76 files) Every browserbase.github.io/stagehand-eval-sites/ URL across evals tasks, sdk-ts tests, the TS/Python/Go examples and the docs is now the Vercel URL. git grep 'github\.io/stagehand-eval-sites' matches only get url.ts . packages/evals/core/tasks/page-info/get url.ts stored the host as an escaped regex. Its allowlist now accepts both hosts. oxfmt reflowed lines where the shorter URL now fits on one line. Apart from get url.ts , each file matches main once the host is normalized and whitespace and commas are ignored. Verified against the Vercel host All 114 files under sites/ are…

Agent parse

Actionable summary

Treat stagehand-python@4.2.0a0.dev1587: Point eval sites at Vercel instead of GitHub Pages ( 3141) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.

Agent usefulness
77/100
Confidence
96%
Canonical data
JSON + Markdown
Next actions

What builders should check

  • Review the official Browserbase Stagehand releases release notes before upgrading.
  • Check compatibility, migration, and security notes against your current agent stack.
  • Run focused regression tests before production rollout.
Classification

Tags and routing

browserbasebrowser-agentautomation
Related signals

Continue the thread