Skip to content

LTS-4750: drop extract-zip via @puppeteer/browsers 3.x override (GHSA-jmr9-qjv8-65gv) #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SaranshBS merged 1 commit into from
Aug 14, 2026
+407 −171
Merged

LTS-4750: drop extract-zip via @puppeteer/browsers 3.x override (GHSA-jmr9-qjv8-65gv) #22

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions .npmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,12 @@
# postinstalls (edgedriver/geckodriver) are not needed. browserstack-node-sdk is
# pinned to the latest release (1.61.0) so no update-postinstall is needed either.
#
# engine-strict=true enforces the package.json `engines.node` floor (>=18), which
# matches our runner pod and what @wdio/cli 9 already requires. Customers on EOL
# Node (<18) get a clear upgrade message instead of obscure failures.
# engine-strict=true enforces the package.json `engines.node` floor (>=22.12.0).
# The floor was raised from >=18 for LTS-4750: the only fix for the unpatched
# extract-zip path traversal (GHSA-jmr9-qjv8-65gv) is @puppeteer/browsers 3.x,
# which is ESM-only and requires Node >=22.12.0. Node 18 (EOL 2025-04-30) and
# Node 20 (EOL 2026-04-30) are both out of support anyway, so customers on EOL
# Node get a clear upgrade message instead of obscure failures.

strict-ssl=true
save-exact=true
Expand Down
Loading
Loading