Repository navigation
Conversation
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
marked this pull request as ready for review
October 28, 2026 18:49
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
Dependency audit on current main is already clean, and a fresh
npm auditafter 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.
lighthouse13.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-launcher1.2.1 → 1.2.2. Lighthouse 13.6 requires it. The launcher passes--remote-debugging-port=0and reads the port Chrome actually opened, and it fixes a Windows temp-profile teardown error.playwright1.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 cifrom the refreshed lockfile succeeds, andnpm auditreports zero vulnerabilities.AGE-484 AGE-485