stagehand-python@4.3.1a0.dev1656: chore : make TS cookbooks use catalog deps ( 3335)
Browserbase Stagehand releases published stagehand-python@4.3.1a0.dev1656: chore : make TS cookbooks use catalog deps ( 3335). why to keep dependencies aligned across the monorepo what changed deleted old golang cookbooks changed cookbook dependencies to point to workspace catalog dependencies updated clone, install, build, & run instructions for ts…
原始内容为英文;当前页面提供中文导航与来源说明,具体事实请以原文为准。
为什么值得关注
Browserbase Stagehand releases published stagehand-python@4.3.1a0.dev1656: chore : make TS cookbooks use catalog deps ( 3335). 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: why to keep dependencies aligned across the monorepo what changed deleted old golang cookbooks changed cookbook dependencies to point to workspace catalog dependencies updated clone, install, build, & run instructions for ts cookbooks Summary by cubic Migrates TypeScript cookbooks to the monorepo workspace catalog so their dependencies stay aligned with the rest of the repo, and removes the Go cookbook ports. Cookbooks now resolve @browserbasehq/stagehand from the workspace and other deps from the root pnpm catalog; their standalone lockfiles and workspaces are deleted. Runner builds the local SDK before starting a cookbook, and TS cookbook instructions now run from the repo root with just cookbook instead of per-folder installs. Docs and READMEs drop Go as a supported cookbook language and reflect the new setup and run commands. pnpm-workspace.yaml and turbo.json gain the cookbook…
可执行摘要
Treat stagehand-python@4.3.1a0.dev1656: chore : make TS cookbooks use catalog deps ( 3335) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent 实用度
- 77/100
- 可信度
- 96%
- 机器格式
- JSON + Markdown
开发者应核对什么
- 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.