Bump joi and gatsby

[dependabot]

Removes joi. It's no longer used after updating ancestor dependency gatsby. These dependencies need to be updated together.

Removes joi

Updates gatsby from 1.9.250 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, prepare scripts that run during installation. Review the package contents before updating.

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@​1.9.261 ⏵ 2.24.68	-6

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 clipboardy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/gatsby@2.24.68 → npm/clipboardy@2.3.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/clipboardy@2.3.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 damerau-levenshtein is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/gatsby@2.24.68 → npm/damerau-levenshtein@1.0.8 ℹ 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/damerau-levenshtein@1.0.8. 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 eslint-plugin-react is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/gatsby@2.24.68 → npm/eslint-plugin-react@7.37.5 ℹ 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/eslint-plugin-react@7.37.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 eslint is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/gatsby@2.24.68 → npm/eslint@6.8.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/eslint@6.8.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 webpack-dev-middleware is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/gatsby@2.24.68 → npm/webpack-dev-middleware@3.7.3 ℹ 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/webpack-dev-middleware@3.7.3. 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 webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/gatsby@2.24.68 → npm/webpack@4.47.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/webpack@4.47.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.

View full report