-
Notifications
You must be signed in to change notification settings - Fork 8
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
chore: upgrade graphql #387
Conversation
WalkthroughThe pull request updates the Changes
Possibly related PRs
Suggested labels
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🔇 Additional comments (2)package.json (2)
The upgrade of graphql-ws to v5.16.0 aligns well with the GraphQL upgrade. This is a compatible minor version bump. Let's verify the compatibility between these versions: ✅ Verification successfulBased on the output, I can generate the final response as we have received the peer dependency information showing that [email protected] is compatible with graphql versions ✓ graphql-ws v5.16.0 is compatible with graphql v16.9.0 The peer dependency check confirms that graphql-ws v5.16.0 supports graphql versions up to v16, making it fully compatible with graphql v16.9.0 used in this project. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check if graphql-ws v5.16.0 is compatible with graphql v16.9.0
echo "Checking graphql-ws peer dependencies..."
npm info [email protected] peerDependencies
Length of output: 465
The upgrade from v16.7.1 to v16.9.0 is a step in the right direction to address the security vulnerabilities. The version is consistently updated in both Let's verify if this version specifically addresses the reported vulnerabilities: Also applies to: 57-57 Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
* chore: update eth proto to latest * refactor: updating to latest graphql schema since featureflags don't include spot & perp (#385) * fix: test * fix: test * chore: upgrade graphql (#387) * refactor: adding eth & tokenfactory types (#389) * refactor: adding eth & tokenfactory types * chore: remove test file * fix: typo * refactor: wasmclient doesn't need nibi registry --------- Co-authored-by: Calico Nino <[email protected]>
## [6.0.0](v5.0.3...v6.0.0) (2024-12-02) ### Bug Fixes * test ([9d7ff5c](9d7ff5c)) * test ([e0b49c9](e0b49c9)) ### Miscellaneous Chores * update eth proto to latest ([96014f2](96014f2)) * upgrade graphql ([#387](#387)) ([d707e12](d707e12)) ### Code Refactors * adding eth & tokenfactory types ([#389](#389)) ([8c6c34c](8c6c34c)) * updating to latest graphql schema since featureflags don't include spot & perp ([#385](#385)) ([cbb36d7](cbb36d7)) [skip ci]
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Mitigate GraphQL Vulnerabilities, brought up by ecosystem projects
Summary by CodeRabbit
graphql
andgraphql-ws
, potentially introducing new features and improvements.