fix(deps): update dependency graphql-request to v5.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
graphql-request	5.1.0 -> 5.2.0

---

Release Notes

jasonkuhrt/graphql-request (graphql-request)

v5.2.0

Compare Source

Features

• cb79d67 make package hybrid ESM/CJS closes #​192 (#​455)

Fixes

• d5a4012 batchRequests type constraint (#​462)
• 4302ba1 check if property errors from response is an empty array (#​454)

Improvements

• 0fb7062 refactor: introduce eslint
• d7d0a8d refactor: typo bathching -> batching (#​425)

Chores

• 7bf2d10 fix githubToken passing
• ff372f5 update pnpm to v7.28.0 (#​463)
• 181ca5c update dependency @​vitest/coverage-c8 to ^0.29.0 (#​461)
• 9dc1b7e vscode settings for project
• 074fb06 add isuee templates
• 29d09e5 mention esm
• 7abfa6d update pnpm to v7.27.1 (#​456)
• 3618169 update pnpm to v7.27.0 (#​452)
• 6487093 update pnpm to v7.26.3 (#​450)
• 0a65e91 update pnpm to v7.26.2 (#​447)
• a23b294 update pnpm to v7.26.1 (#​445)
• 0962dd2 switch to pnpm (#​444)
• 99f6763 update dev deps (#​443)
• 7a644e7 remove security policy
• 9a097f2 attribute owner and author to Jason Kuhrt

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @graphql-codegen/[email protected]
npm error Found: [email protected]
npm error node_modules/graphql-request
npm error   graphql-request@"5.2.0" from the root project
npm error   graphql-request@"^5.0.0" from @graphql-tools/[email protected]
npm error   node_modules/@graphql-tools/prisma-loader
npm error     @graphql-tools/prisma-loader@"^7.2.49" from @graphql-codegen/[email protected]
npm error     node_modules/@graphql-codegen/cli
npm error       dev @graphql-codegen/cli@"2.16.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql-request@"^3.4.0 || ^4.0.0 || ~5.0.0 || ~5.1.0" from @graphql-codegen/[email protected]
npm error node_modules/@graphql-codegen/typescript-graphql-request
npm error   dev @graphql-codegen/typescript-graphql-request@"4.5.9" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/graphql-request
npm error   peer graphql-request@"^3.4.0 || ^4.0.0 || ~5.0.0 || ~5.1.0" from @graphql-codegen/[email protected]
npm error   node_modules/@graphql-codegen/typescript-graphql-request
npm error     dev @graphql-codegen/typescript-graphql-request@"4.5.9" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-01T13_42_17_436Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-01T13_42_17_436Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @graphql-codegen/[email protected]
npm error Found: [email protected]
npm error node_modules/graphql-request
npm error   graphql-request@"5.2.0" from the root project
npm error   graphql-request@"^5.0.0" from @graphql-tools/[email protected]
npm error   node_modules/@graphql-tools/prisma-loader
npm error     @graphql-tools/prisma-loader@"^7.2.49" from @graphql-codegen/[email protected]
npm error     node_modules/@graphql-codegen/cli
npm error       dev @graphql-codegen/cli@"2.16.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql-request@"^3.4.0 || ^4.0.0 || ~5.0.0 || ~5.1.0" from @graphql-codegen/[email protected]
npm error node_modules/@graphql-codegen/typescript-graphql-request
npm error   dev @graphql-codegen/typescript-graphql-request@"4.5.9" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/graphql-request
npm error   peer graphql-request@"^3.4.0 || ^4.0.0 || ~5.0.0 || ~5.1.0" from @graphql-codegen/[email protected]
npm error   node_modules/@graphql-codegen/typescript-graphql-request
npm error     dev @graphql-codegen/typescript-graphql-request@"4.5.9" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-08-01T07_33_07_611Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-01T07_33_07_611Z-debug-0.log

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.