Migrating from 0.x.x - Anchor Browser Docs

Version 1.0.0 of both SDKs is generated directly from the public OpenAPI specification, and every method is named after its API operation. If you are upgrading from any release prior to 1.0.0 (all 0.x.x versions, and the 1.0.0-dev pre-releases on PyPI), method names have changed — for example:

- const session = await client.sessions.create({ session: { recording: { active: false } } });
+ const session = await Sessions.createSession({ body: { session: { recording: { active: false } } } });

- session = client.sessions.create(session={"recording": {"active": False}})
+ session = client.sessions.create_session(session={"recording": {"active": False}})

In TypeScript the client itself also changed (a shared configurable instance instead of a constructed class); in Python the client construction, error types, retries and timeouts are unchanged — only method names and a few subsurfaces moved.

Requirements

TypeScript: no runtime requirement changes.
Python: Python 3.10+ (was 3.9+) and pydantic v2 (>= 2, < 3) — pydantic v1 is no longer supported, and pip will refuse to resolve anchorbrowser >= 1.0.0 alongside pydantic < 2. Every other dependency keeps the same version range.

Full migration guides

Each repository ships a complete guide covering every breaking change and its 1.0 equivalent, including the full method rename table:

TypeScript: MIGRATION.md
Python: MIGRATION.md

​Requirements

​Full migration guides

Requirements

Full migration guides