Repository navigation
Prepare 2.0.5 for the browser-tools CLI - #255
Merged
Merged
Conversation
Publish checklist (Ted)After this merges, from a clean worktree of that
This PR does not publish, tag, or release. |
cursor
Bot
force-pushed
the
cursor/prep-2.0.5-8db9
branch
from
October 27, 2026 04:24
aa0a194 to
7038362
Compare
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
browser-toolsCLI 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-mcpand@agentdeskai/browser-tools-serverare 2.0.5. The server depends on^2.0.5.server.jsonis 2.0.5 (top-level and the npm package entry). The private workspace root has no version field.browser-toolsbin from Browser Tools CLI with MCP parity and navigate (AGE-482) #252.## 2.0.5covers CLI parity andnavigateBrowser.## 2.0.4now 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 typecheckandnpm run buildpassednpm test: 34 files, 558 tests passednpm run test:e2e: 5 files, 72 tests passednpm audit --audit-level=moderate: 0 vulnerabilities