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

refactor: Security upgrade graphql from 16.6.0 to 16.8.1 #8757

Merged
merged 1 commit into from
Sep 22, 2023

Conversation

parseplatformorg
Copy link
Contributor

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:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-JS-GRAPHQL-5905181
No Proof of Concept

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

Commit messages
Package name: graphql The new version differs by 10 commits.

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:

🦉 Denial of Service (DoS)

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Security upgrade graphql from 16.6.0 to 16.8.1 refactor: Security upgrade graphql from 16.6.0 to 16.8.1 Sep 20, 2023
@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@codecov
Copy link

codecov bot commented Sep 20, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (6458ab0) 94.11% compared to head (f6c4486) 94.11%.
Report is 1 commits behind head on release-5.x.x.

❗ Current head f6c4486 differs from pull request most recent head ce2ad82. Consider uploading reports for the commit ce2ad82 to get more accurate results

Additional details and impacted files
@@              Coverage Diff               @@
##           release-5.x.x    #8757   +/-   ##
==============================================
  Coverage          94.11%   94.11%           
==============================================
  Files                184      184           
  Lines              13809    13809           
==============================================
  Hits               12997    12997           
  Misses               812      812           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mtrezza mtrezza merged commit 0bb63d8 into release-5.x.x Sep 22, 2023
27 of 28 checks passed
@mtrezza mtrezza deleted the snyk-fix-9ddfea69e31df16b2156fec08bb8a785 branch September 22, 2023 01:27
@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 5.5.6

@parseplatformorg parseplatformorg added the state:released-5.x.x Released as LTS version label Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released-5.x.x Released as LTS version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants