Skip to content

Track current stable Chrome in audits and end-to-end tests - #261

Open
tedjames wants to merge 1 commit into
mainfrom
cursor/chrome-deps-audit-da73
Open

tedjames wants to merge 1 commit into
mainfrom
cursor/chrome-deps-audit-da73

Conversation

@tedjames

Copy link
Copy Markdown
Member

Summary

Dependency audit on current main is already clean, and a fresh npm audit after this bump is still clean: no info, low, moderate, high, or critical findings in the full tree or in production dependencies. The dependency-audit job on the latest main run is green. Nothing was left unpatched.

The only dependency moves are the ones that talk to Chrome or test it. Current stable Chrome is 156. Other direct dependencies (MCP SDK, express, ws, zod, TypeScript, Vitest) stay where they are. Windows CI and the Vitest 5 / connector work from #247 and #250 are untouched. This does not publish or tag.

  • lighthouse 13.4.1 → 13.6.0. 13.4.1 shipped against the Chrome 152 DevTools protocol. 13.6 is the current release and is what the audit tools now run.
  • chrome-launcher 1.2.1 → 1.2.2. Lighthouse 13.6 requires it. The launcher passes --remote-debugging-port=0 and reads the port Chrome actually opened, and it fixes a Windows temp-profile teardown error.
  • playwright 1.62.1 → 1.64.1. End-to-end tests were launching Chromium 151. They now load the extension in Chromium 156.0.8078.4, the same stable branch as desktop Chrome 156.

Tests

  • npm ci from the refreshed lockfile succeeds, and npm audit reports zero vulnerabilities.
  • Typecheck, build, 599 unit and integration tests, and 73 end-to-end tests pass locally. The end-to-end suite ran on Chromium 156.0.8078.4, including a real Lighthouse audit.

AGE-484 AGE-485

Open in Web Open in Cursor 

Lighthouse 13.6 and chrome-launcher 1.2.2 launch audits against Chrome 156.
Playwright 1.64 runs the extension suite on Chromium 156. npm audit is clean;
other dependencies stay put.

AGE-484 AGE-485

Co-authored-by: werbel.ted <werbel.ted@gmail.com>
@tedjames
tedjames marked this pull request as ready for review October 28, 2026 18:49
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