puppeteer

vbrowsers-v3.0.1 scope: browsers Maintenance

This release keeps dependencies and maintenance posture current for teams operating this tool.

Published 21d Developer Productivity

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

automation chrome chromium developer-tools firefox headless-chrome

+3 more

node-module testing web

ReleasePort's take

Light signal

editorial:auto 13d

Puppeteer 3.0.1 includes minor fixes. The release involves browser dependency changes that may require validation in development environments.

Why it matters: Browser dependency updates may affect test execution. Verify Puppeteer integration works with updated dependencies before rolling out to production use.

Summary

AI summary

Minor fixes and improvements.

Changes in this release

Type	Severity	Summary	CVE
Bugfix	Medium	Update browsers to trigger release. Update browsers to trigger release. Source: llm_adapter@2026-05-21 Confidence: low	—

Full changelog

3.0.1 (2026-05-13)

🛠️ Fixes

update browsers to trigger release (#14984) (bf05fb9)

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track puppeteer

Get notified when new releases ship.

About puppeteer

All releases →

Related context

Related tools

Earlier breaking changes

vbrowsers-v3.0.0 Public makeProgressCallback helper function removed.
vbrowsers-v3.0.0 Switched from extract-zip to OS native tar/unzip.
vbrowsers-v3.0.0 Proxy agent made optional peer dependency, upgraded to v8.
vbrowsers-v3.0.0 Minimum Node.js v20.19 and TypeScript v5.0.1 required.
vbrowsers-v3.0.0 Minimum Node.js version bumped to 22.