Skip to content

Update dependency graphql-request to v7 #261

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency graphql-request to v7 #261

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 10, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
graphql-request (source) ^6.1.0 -> ^7.0.0 age confidence

Release Notes

graffle-js/graffle (graphql-request)

v7.3.1

Compare Source

Bug Fixes

  • Fixed broken example links on npmjs.com (#​1332)
    • Updated package.json repository metadata to point to correct location: graffle-js/graffle
    • Updated homepage URL to include /tree/graphql-request path
    • Updated bugs URL to point to correct issues page
    • All example links on npm now correctly resolve to files in the graphql-request branch

Links

v7.3.0: graphql-request v7.3.0

Compare Source

What's Changed

Features
  • CommonJS Support: Added CommonJS module format () alongside ESM for better compatibility with Jest and other testing environments that aren't fully ESM-ready
  • Improved Type Defaults: Default type parameters to any for easier migration and reduced type friction
Pull Requests
  • feat(graphql-request): default types any and support common js #​1396

Contributors

Thanks to @​Moumouls (Antoine Cormouls) for the contribution! 🚀

Installation:

npm install graphql-request@7.3.0

Package: https://www.npmjs.com/package/graphql-request/v/7.3.0

v7.2.0: graphql-request@7.2.0

Compare Source

Features:

v7.1.2: graphql-request@7.1.2

Compare Source

Fixes:

  • b732f45 Remove reference to type-fest which is not a dependency.

v7.1.1: graphql-request@7.1.1

Compare Source

Fixes
  • 37445c8 Support CJS and remove Graffle code. To use Graffle by now, you should be using pnpm add graffle@next.

v7.1.0

Compare Source

Fixes
Improvements
  • 30b39bf improve: update all deps to latest (#​936)
  • 92ea1b2 docs: mention additional requirement for TS
  • 39dfb37 refactor: no mock server
  • db4db92 docs: TS moduleResolution requirements
Graffle
Features
Chores

v7.0.1

Compare Source

Fixes
  • dc299d9 no node fs module in runtime
Improvements
  • 11805c8 improve: remove needless deep imports into graphql
Chores

v7.0.0

Compare Source

BREAKING CHANGES
  • 2a121c6 remove inlined graphql websocket code
  • 99a192e add spec compliant default Accept header (#​618)
  • 0e53aed replace GraphQLClientRequestHeaders with built-in HeadersInit type (#​616)
  • c3a309f remove support for CommonJS (#​607)
  • 6efcc0d remove cross-fetch polyfill
  • Valid URL must be passed (no more path-only strings like /foo) (#​745)
Features
Fixes
Improvements

Graffle (alpha)

Features

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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
Copy link
Contributor Author

renovate bot commented May 10, 2024 •
edited
Loading

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @graphql-codegen/typescript-graphql-request@5.0.0
npm ERR! Found: graphql-request@7.3.1
npm ERR! node_modules/graphql-request
npm ERR!   graphql-request@"^7.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql-request@"^6.0.0" from @graphql-codegen/typescript-graphql-request@5.0.0
npm ERR! node_modules/@graphql-codegen/typescript-graphql-request
npm ERR!   dev @graphql-codegen/typescript-graphql-request@"^5.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: graphql-request@6.1.0
npm ERR! node_modules/graphql-request
npm ERR!   peer graphql-request@"^6.0.0" from @graphql-codegen/typescript-graphql-request@5.0.0
npm ERR!   node_modules/@graphql-codegen/typescript-graphql-request
npm ERR!     dev @graphql-codegen/typescript-graphql-request@"^5.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --no-strict-peer-deps, --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-10-21T21_48_17_588Z-debug-0.log

@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 914a4bd to 8a48459 Compare August 10, 2025 15:02
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 8a48459 to 16d579b Compare September 25, 2025 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant