-
Notifications
You must be signed in to change notification settings - Fork 17
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
Bump graphql-request from 6.1.0 to 7.0.1 #700
Conversation
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake 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 [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Bumps [graphql-request](https://github.com/jasonkuhrt/graphql-request) from 6.1.0 to 7.0.1. - [Release notes](https://github.com/jasonkuhrt/graphql-request/releases) - [Commits](jasonkuhrt/graphql-request@6.1.0...7.0.1) --- updated-dependencies: - dependency-name: graphql-request dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
3a6c06d
to
bb05110
Compare
Superseded by #719. |
Bumps graphql-request from 6.1.0 to 7.0.1.
Release notes
Sourced from graphql-request's releases.
... (truncated)
Commits
dc299d9
fix: no node fs module in runtimeecf5032
chore(deps): update dependency tsx to v4.9.4 (#843)c15f7f9
fix: type import11805c8
improve: remove needless deep imports into graphql12cb8cf
chore(deps): update dependency zod to v3.23.8 (#836)be48f1e
feat: rename cli to grafflee1e3e58
chore(deps): update dependency@types/node
to v20.12.11 (#835)7452c47
chore(deps): update dependency zod to v3.23.7 (#834)b2c0a2a
chore(deps): update dependency happy-dom to v14.10.1 (#832)aa53f3a
chore(deps): update dependency@types/node
to v20.12.10 (#833)You can trigger a rebase of this PR 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 merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)