Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 6, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@browserbasehq/[email protected]

Patch Changes

@browserbasehq/[email protected]

Patch Changes

@browserbasehq/[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch from 0a6a0e5 to 9ea1042 Compare August 6, 2025 22:05
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greptile Summary

This PR is an automated changeset release that bumps the Stagehand library and related packages to new patch versions. The main change is updating the core @browserbasehq/stagehand library from version 2.4.2 to 2.4.3, with corresponding version bumps for the evals (1.0.6 → 1.0.7) and examples (1.0.6 → 1.0.7) packages.

The primary functional change is expanding Zod version compatibility in the main library's peer dependencies from supporting only Zod v3 (>=3.25.0 <4.0.0) to supporting both v3 and v4 (>=3.25.0 <4.1.0). This change also includes adding "pathing spec" support, which likely relates to how schema paths are handled between Zod versions.

All changes follow the established monorepo patterns using Changesets for automated releases. The evals and examples packages don't contain direct changes but receive version bumps because they depend on the main Stagehand library via workspace dependencies. The changelog entries are automatically generated with proper commit references and maintain consistency with the existing format across all three packages.

Confidence score: 5/5

  • This PR is extremely safe to merge with minimal risk as it's an automated dependency compatibility update
  • Score reflects the straightforward nature of expanding supported dependency versions while maintaining backward compatibility
  • No files require special attention as all changes are routine version bumps and changelog updates

6 files reviewed, no comments

Edit Code Review Bot Settings | Greptile

@github-actions github-actions bot force-pushed the changeset-release/main branch 10 times, most recently from 5f300be to 508ad1a Compare August 14, 2025 01:37
@github-actions github-actions bot force-pushed the changeset-release/main branch from 508ad1a to dc2600f Compare August 19, 2025 18:24
@miguelg719 miguelg719 merged commit b52e4f9 into main Aug 19, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant