Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade gatsby from 2.32.13 to 5.0.0 #448

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

YoshiWalsh
Copy link
Collaborator

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • examples/with-serverless/package.json
    • examples/with-serverless/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 608/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 4.3
Information Exposure
SNYK-JS-GATSBY-5671647
Yes Proof of Concept
medium severity 608/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 4.3
Information Exposure
SNYK-JS-GATSBYCLI-5671903
Yes Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: gatsby The new version differs by 250 commits.
  • 0c6cd61 chore(release): Publish
  • 5e8e621 chore: Update main README (#36954)
  • 7130cd4 test(gatsby): Slices API integration tests (#36747)
  • 6496eed chore(release): Publish next
  • bc7ac84 chore: preserve previous webpack stats derived values, even if we restart webpack itself (#36980)
  • 2b5af32 fix: drop `__renderedByLocation` prop when calculating slice props hashes and don't expose it to slice component (#36979)
  • cc1ee9b chore(release): Publish next
  • 6a53861 chore(gatsby-link): Correct type export (#36968)
  • 0ad6314 fix(gatsby-graphiql-explorer): Use upstream exporter package (#36966)
  • 964265c chore(release): Publish next
  • b624442 chore: Update peerDeps (#36965)
  • b2ab092 chore(release): Publish next
  • e2a14bf feat(gatsby): Slices <> partial hydration interop (#36960)
  • 0083e62 fix(deps): update starters and examples gatsby packages to ^4.24.7 (#36957)
  • 68e9cab chore(changelogs): update changelogs (#36958)
  • b9eb8d2 chore(deps): update dependency autoprefixer to ^10.4.13 for gatsby-plugin-sass (#36934)
  • 58c37ea chore(deps): update dependency @ jridgewell/trace-mapping to ^0.3.17 for gatsby-legacy-polyfills (#36933)
  • a5e4c47 fix(deps): update dependency body-parser to ^1.20.1 for gatsby-source-drupal (#36940)
  • c86aa7e chore(docs): Add clarification for Pro Tip on Part 4 of tutorial (#36918)
  • d5c775a feat(gatsby): handle graphql-import-node bundling (#36951)
  • 59e2976 feat(gatsby-remark-embed-snippet): added csproj to language map so it will be recognized as xml (#36919)
  • c8a7dda chore(docs): Valhalla Content Hub Reference Guide (#36949)
  • 3044280 fix(gatsby): stitch slices if just page html was regenerating without any of used slices regenerating (#36950)
  • 10abdcb chore(release): Publish next

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


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

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

…/package-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-GATSBY-5671647
- https://snyk.io/vuln/SNYK-JS-GATSBYCLI-5671903
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants