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] Upgrade graphql-jit from 0.8.4 to 0.8.7 #10604

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mattkrick
Copy link
Member

snyk-top-banner

Snyk has created this PR to upgrade graphql-jit from 0.8.4 to 0.8.7.

ℹ️ 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 10 versions ahead of your current version.

  • The recommended version was released on 2 months ago.

Release notes
Package name: graphql-jit from graphql-jit GitHub release notes

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.

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:

Snyk has created this PR to upgrade graphql-jit from 0.8.4 to 0.8.7.

See this package in npm:
graphql-jit

See this project in Snyk:
https://app.snyk.io/org/mattkrick/project/d35f1a72-9f4f-43ee-b8c4-498148a93f17?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link
Contributor

@Dschoordsch Dschoordsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's an issue with yarn build --no-deps with this package which needs to be fixed when updating

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants