Files
chrome-use/.changeset
Chris Tate fbcab375b0 chore: prepare v0.23.1 release (#1089)
* chore: add patch changeset for v0.23.1 release

Add changeset covering 7 commits since v0.23.0: auto-dialog dismissal,
Puppeteer cache fallback, console output improvements, same-document
navigation fix, cross-domain save_state, external tab detection in CDP
mode, and dashboard hot-reload.

Fill documentation gaps: Puppeteer/Brave in browser discovery tables,
console --json args field, AGENT_BROWSER_NO_AUTO_DIALOG env var in
SKILL.md.

* chore: point package.json homepage to agent-browser.dev
2026-03-30 13:12:07 -05:00
..
2026-01-23 11:19:43 -06:00
2026-01-23 11:19:43 -06:00

Changesets

This project uses Changesets for versioning and changelog generation.

Adding a changeset

When you make a change that should be released, run:

pnpm changeset

This will prompt you to:

  1. Select the type of change (patch, minor, major)
  2. Write a summary of your changes

The changeset file will be committed with your PR.

Release process

When changesets are merged to main, the release workflow will:

  1. Create a "Version Packages" PR that updates version numbers and changelogs
  2. When that PR is merged, packages are automatically published to npm