[Snyk] Upgrade gatsby from 5.0.0 to 5.14.1

[X-oss-byte]

Snyk has created this PR to upgrade gatsby from 5.0.0 to 5.14.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 147 versions ahead of your current version.

• The recommended version was released 2 months ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	410	No Known Exploit
	Uncaught Exception SNYK-JS-SOCKETIO-7278048	410	No Known Exploit
	Denial of Service (DoS) SNYK-JS-SOCKETIOPARSER-5596892	410	No Known Exploit
	Sandbox Bypass SNYK-JS-WEBPACK-3358798	410	Proof of Concept
	Path Traversal SNYK-JS-WEBPACKDEVMIDDLEWARE-6476555	410	Proof of Concept
	Denial of Service (DoS) SNYK-JS-ENGINEIO-3136336	410	No Known Exploit
	Denial of Service (DoS) SNYK-JS-WS-7266574	410	Proof of Concept
	Cross-site Scripting (XSS) SNYK-JS-WEBPACK-7840298	410	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	410	Proof of Concept
	Information Exposure SNYK-JS-GATSBY-5671647	410	Proof of Concept
	Information Exposure SNYK-JS-GATSBYCLI-5671903	410	Proof of Concept
	Denial of Service (DoS) SNYK-JS-GRAPHQL-5905181	410	Proof of Concept
	Open Redirect SNYK-JS-EXPRESS-6474509	410	No Known Exploit
	Cross-site Scripting SNYK-JS-EXPRESS-7926867	410	No Known Exploit
	Cross-site Scripting SNYK-JS-SERVESTATIC-7926865	410	No Known Exploit
	Cross-site Scripting SNYK-JS-SEND-7926862	410	No Known Exploit

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Bug Fixes:

• Upgrade gatsby from 5.0.0 to 5.14.1 to address multiple vulnerabilities, including asymmetric resource consumption, uncaught exceptions, denial of service, sandbox bypass, path traversal, information exposure, open redirect, and cross-site scripting issues across various dependencies such as body-parser, socket.io, webpack, engine.io, ws, path-to-regexp, gatsby, gatsby-cli, graphql, express, serve-static, and send. See the linked Snyk reports for details on the individual vulnerabilities

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b74a15e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the gatsby dependency from version 5.0.0 to 5.14.1. The update includes changes to package.json and yarn.lock.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
The pull request upgrades the gatsby dependency from version 5.0.0 to 5.14.1. This involves updating the version specified in package.json and updating the dependency information in yarn.lock.	Updated gatsby version from 5.0.0 to 5.14.1 in package.json. Updated the yarn.lock file to reflect the new gatsby version and its dependencies.	package.json yarn.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!