Skip to content

Prepare 2.0.5 for the browser-tools CLI - #255

Merged
cursor[bot] merged 2 commits into
mainfrom
cursor/prep-2.0.5-8db9
Oct 27, 2026
Merged

cursor[bot] merged 2 commits into
mainfrom
cursor/prep-2.0.5-8db9

Conversation

@tedjames

Copy link
Copy Markdown
Member

Summary

The browser-tools CLI landed on main in #252 after the 2.0.4 npm publish (commit 936272d). This prepares 2.0.5 so that CLI can be published. It does not publish to npm, tag, or cut a GitHub release.

  • @agentdeskai/browser-tools-mcp and @agentdeskai/browser-tools-server are 2.0.5. The server depends on ^2.0.5.
  • server.json is 2.0.5 (top-level and the npm package entry). The private workspace root has no version field.
  • The lockfile records the browser-tools bin from Browser Tools CLI with MCP parity and navigate (AGE-482) #252.
  • CHANGELOG ## 2.0.5 covers CLI parity and navigateBrowser. ## 2.0.4 now states the Harden eval and input capability gates #251 capability gates, which were in the 2.0.4 npm tarball but not in that section. The 2.0.4 npm publish was hardening only.

The Chrome extension manifest stays 2.0.4. Navigate support is already in the extension on main; this cut is the npm packages.

Tests

  • npm run typecheck and npm run build passed
  • npm test: 34 files, 558 tests passed
  • npm run test:e2e: 5 files, 72 tests passed
  • npm audit --audit-level=moderate: 0 vulnerabilities
Open in Web Open in Cursor 

@cursor

cursor Bot commented Oct 27, 2026

Copy link
Copy Markdown

Publish checklist (Ted)

After this merges, from a clean worktree of that main commit (do not publish from a dirty tree):

  1. Worktree: git fetch origin main && git worktree add ../browser-tools-mcp-2.0.5 origin/main
  2. npm publish in browser-tools-mcp first (prepublishOnly builds). Confirm @agentdeskai/browser-tools-mcp@2.0.5 is on the registry and that the browser-tools bin is in the tarball.
  3. Then npm publish in browser-tools-server (it depends on @agentdeskai/browser-tools-mcp@^2.0.5).
  4. Tag that commit v2.0.5 and push the tag.
  5. gh release create v2.0.5 with the ## 2.0.5 changelog section (title 2.0.5, same shape as v2.0.4).

This PR does not publish, tag, or release.

The 2.0.4 npm publish was cut from 936272d and does not include the CLI. Bump the published packages and record CLI parity, navigate, and the capability gates from #251.

Co-authored-by: werbel.ted <werbel.ted@gmail.com>
@cursor
cursor Bot force-pushed the cursor/prep-2.0.5-8db9 branch from aa0a194 to 7038362 Compare October 27, 2026 04:24
The uncaught-error check required every buffered entry to be level error.
Fetches and the late timer on the fixture page can log after injection, so
that assertion failed when those landed during the wait. Only the injected
error messages need to be error level.

Co-authored-by: werbel.ted <werbel.ted@gmail.com>
@cursor
cursor Bot merged commit f575e0f into main Oct 27, 2026
8 checks 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.

2 participants