stagehand-python@4.2.2a0.dev1615: fix : align bb transport behaviour across SDKs ( 3229)
Browserbase Stagehand releases published stagehand-python@4.2.2a0.dev1615: fix : align bb transport behaviour across SDKs ( 3229). why to address comments on earlier PRs in this stack what changed aligned request-header handling across SDKs. HTTP clients supply host & transfer headers; SDKs supply the Browserbase key & Gateway session header. ordinary…
原始内容为英文;当前页面提供中文导航与来源说明,具体事实请以原文为准。
为什么值得关注
Browserbase Stagehand releases published stagehand-python@4.2.2a0.dev1615: fix : align bb transport behaviour across SDKs ( 3229). 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 address comments on earlier PRs in this stack what changed aligned request-header handling across SDKs. HTTP clients supply host & transfer headers; SDKs supply the Browserbase key & Gateway session header. ordinary application headers remain supported. malformed headers fail before HTTP dispatch, so Go no longer reports them as retryable network failures. preserved non-ASCII response header bytes in Python so the worker can reconstruct the response without rejecting its headers. cancelled pending TypeScript Browserbase requests when the browser closes, including when the socket does not deliver another close event. reused Python HTTP connections across requests on the same RPC connection, closing the pool after pending requests are cancelled during cleanup. skipped cache request bodies larger than 25 MB (25,000,000 UTF-8 bytes) before sending them over RPC. normal execution…
可执行摘要
Treat stagehand-python@4.2.2a0.dev1615: fix : align bb transport behaviour across SDKs ( 3229) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent 实用度
- 72/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.