-
Notifications
You must be signed in to change notification settings - Fork 164
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(deps): update @graphql-codegen dependencies #773
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: b0c5e5f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
38c00f6
to
b739b6b
Compare
Sorry. |
I have resolved the conflicts in the yarn.lock file. |
@dotansimha I would appreciate it if you could review it. |
Hey hey, what's blocking this? Can I help somehow? @dotansimha |
Related older PR from Renovate (abandoned): #609 Is there a way to proceed with either of the PRs? |
🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
the pull request.
Description
This PR updates outdated packages in the @graphql-codegen/near-operation-file-preset to their latest versions. The update aims to ensure compatibility and access to the latest features and improvements, thereby maintaining the overall stability and security of the project.
Related #772
Type of change
Please delete options that are not relevant.
expected)
Screenshots/Sandbox (if appropriate/relevant):
codesandbox
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration
yaml test
Test Environment:
Checklist:
CONTRIBUTING doc and the
style guidelines of this project
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose
the solution you did and what alternatives you considered, etc...