Skip to content

Commit

Permalink
[Snyk] Upgrade graphql from 16.9.0 to 16.10.0 (#1173)
Browse files Browse the repository at this point in the history
* fix: upgrade graphql from 16.9.0 to 16.10.0

Snyk has created this PR to upgrade graphql from 16.9.0 to 16.10.0.

See this package in yarn:
graphql

See this project in Snyk:
https://app.snyk.io/org/p0nder0sa/project/270b554d-5de8-452f-ad01-8bceb7604a92?utm_source=github&utm_medium=referral&page=upgrade-pr

* update yarn.lock

---------

Co-authored-by: snyk-bot <snyk-bot@snyk.io>
  • Loading branch information
will0684 and snyk-bot authored Feb 11, 2025
1 parent df5fd07 commit 7cb157e
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"cors": "^2.8.5",
"cuid": "^2.1.8",
"focus-trap-react": "^8.11.2",
"graphql": "^16.9.0",
"graphql": "^16.10.0",
"i18next": "^23.16.8",
"i18next-http-backend": "^1.4.5",
"joi": "^17.13.1",
Expand Down
10 changes: 5 additions & 5 deletions yarn.lock
Original file line number Diff line number Diff line change
Expand Up @@ -9216,10 +9216,10 @@ __metadata:
languageName: node
linkType: hard

"graphql@npm:^16.9.0":
version: 16.9.0
resolution: "graphql@npm:16.9.0"
checksum: 5833f82bb6c31bec120bbf9cd400eda873e1bb7ef5c17974fa262cd82dc68728fda5d4cb859dc8aaa4c4fe4f6fe1103a9c47efc01a12c02ae5cb581d8e4029e2
"graphql@npm:^16.10.0":
version: 16.10.0
resolution: "graphql@npm:16.10.0"
checksum: d42cf81ddcf3a61dfb213217576bf33c326f15b02c4cee369b373dc74100cbdcdc4479b3b797e79b654dabd8fddf50ef65ff75420e9ce5596c02e21f24c9126a
languageName: node
linkType: hard

Expand Down Expand Up @@ -14441,7 +14441,7 @@ __metadata:
cypress-localstorage-commands: "npm:^1.4.5"
fetch-mock: "npm:^9.11.0"
focus-trap-react: "npm:^8.11.2"
graphql: "npm:^16.9.0"
graphql: "npm:^16.10.0"
husky: "npm:^9.0.11"
i18next: "npm:^23.16.8"
i18next-http-backend: "npm:^1.4.5"
Expand Down

0 comments on commit 7cb157e

Please sign in to comment.