Bump joi, gatsby and gatsby-plugin-offline

[dependabot]

Removes joi. It's no longer used after updating ancestor dependencies joi, gatsby and gatsby-plugin-offline. These dependencies need to be updated together.

Removes joi

Updates gatsby from 2.0.2 to 2.24.68

Release notes

Sourced from gatsby's releases.

gatsby-source-wordpress@7.13.5 and 6 more...

2024-08-26

Updated packages

• gatsby-source-wordpress@7.13.5
• gatsby-remark-responsive-iframe@6.13.2
• gatsby-remark-prismjs@7.13.2
• gatsby-remark-images@7.13.2
• gatsby-remark-images@6.13.2
• gatsby-remark-graphviz@5.13.2
• gatsby-remark-copy-linked-files@6.13.2
• gatsby-plugin-offline@6.13.3

What's Changed

• fix: pin cheerio (#39066) by @​gatsbybot in gatsbyjs/gatsby#39069

See full release notes: gatsbyjs/gatsby#39070

Commits

• 84fa4be chore(release): Publish
• 49e6669 feat(gatsby-plugin-utils): add package and methods to validate plugin options...
• f3075c9 fix(deps): update minor and patch for gatsby-telemetry (#27145)
• 04c813d chore(gatsby-image): Add more DatoCMS fragments (#27289)
• 7bf2bdb perf(gatsby-source-contentful): fix API, execute deprecations, improve perfor...
• 8ca2826 chore(deps): update dependency eslint-plugin-react to ^7.21.3 (#27279)
• 639a0ca chore(docs): Update storyblok links (#27064)
• 8437b65 chore(docs): Remove --save from READMEs (#27032)
• 52c69bd chore(docs): Update deploying-to-netlify (#25620)
• cc87135 chore(docs): typo in i18n doc (#27284)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by mxstbr, a new releaser for gatsby since your current version.

Install script changes

This version adds postinstall script that runs during installation. Review the package contents before updating.

Updates gatsby-plugin-offline from 2.0.5 to 6.16.0

Release notes

Sourced from gatsby-plugin-offline's releases.

gatsby-source-wordpress@7.13.5 and 6 more...

2024-08-26

Updated packages

• gatsby-source-wordpress@7.13.5
• gatsby-remark-responsive-iframe@6.13.2
• gatsby-remark-prismjs@7.13.2
• gatsby-remark-images@7.13.2
• gatsby-remark-images@6.13.2
• gatsby-remark-graphviz@5.13.2
• gatsby-remark-copy-linked-files@6.13.2
• gatsby-plugin-offline@6.13.3

What's Changed

• fix: pin cheerio (#39066) by @​gatsbybot in gatsbyjs/gatsby#39069

See full release notes: gatsbyjs/gatsby#39070

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

... (truncated)

Changelog

Sourced from gatsby-plugin-offline's changelog.

6.16.0 (2026-01-26)

🧾 Release notes

Features

• support React 19 #39306 (9e39c05)

Bug Fixes

• use more explicit node.js version range #39398 (c355640)

Other Changes

• Revert "chore(release): Publish next pre-minor" (3539ec8)

6.15.0 (2025-08-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-offline

6.14.0 (2024-11-06)

🧾 Release notes

Bug Fixes

• pin cheerio #39066 (e2c3a86)
• handler generation on windows #38900 (c91ed28)

6.13.3 (2024-08-26)

Bug Fixes

• pin cheerio #39066 #39069 (282caaf)

6.13.2 (2024-04-10)

Bug Fixes

• handler generation on windows #38900 #38929 (edaf016)

6.13.1 (2024-01-23)

Note: Version bump only for package gatsby-plugin-offline

6.13.0 (2023-12-18)

🧾 Release notes

... (truncated)

Commits

• 92d6c67 chore(release): Publish
• 3539ec8 Revert "chore(release): Publish next pre-minor"
• c355640 fix: use more explicit node.js version range (#39398)
• aea34d8 chore(release): Publish next pre-minor
• 9e39c05 feat: support React 19 (#39306)
• c03a920 chore(changelogs): update changelogs (#39364)
• 32f2d1e chore(release): Publish next pre-minor
• 17baffb chore(release): Publish next pre-minor
• 5f44fcd chore(changelogs): update changelogs (#39156)
• be577c1 chore(changelogs): update changelogs (#39070)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by serhalp-netlify, a new releaser for gatsby-plugin-offline 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 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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	gatsby-link@​2.0.2 ⏵ 2.11.0			+5	-4
	lodash@​4.17.11 ⏵ 4.18.1	+1	+75	+1
	gatsby-plugin-offline@​2.0.5 ⏵ 6.16.0			+12
	gatsby@​2.0.12 ⏵ 2.24.68	-5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: xmlhttprequest and npm xmlhttprequest-ssl vulnerable to Arbitrary Code Injection CVE: GHSA-h4j5-c7cj-74xg xmlhttprequest and xmlhttprequest-ssl vulnerable to Arbitrary Code Injection (CRITICAL) Affected versions: < 1.6.2 Patched version: 1.6.2 From: ? → npm/gatsby@2.24.68 → npm/xmlhttprequest-ssl@1.5.5 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/xmlhttprequest-ssl@1.5.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: Improper Certificate Validation in npm xmlhttprequest-ssl CVE: GHSA-72mh-269x-7mh5 Improper Certificate Validation in xmlhttprequest-ssl (CRITICAL) Affected versions: < 1.6.1 Patched version: 1.6.1 From: ? → npm/gatsby@2.24.68 → npm/xmlhttprequest-ssl@1.5.5 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/xmlhttprequest-ssl@1.5.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm node-libs-browser is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/node-libs-browser@2.2.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-libs-browser@2.2.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report