Skip to content
This repository was archived by the owner on Nov 3, 2026. It is now read-only.

Update dependency graphql-request to v7 - #261

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/graphql-request-7.x
Open

Update dependency graphql-request to v7#261
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/graphql-request-7.x

Conversation

@renovate

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

Copy link
Copy Markdown
Contributor

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.4.0

Compare Source

What's Changed

Features
  • Expose response headers and body on error responses - Added headers and body properties to GraphQLResponse and GraphQLClientResponse types, making it easier to access non-GraphQL response data (e.g., 401/403/503 errors that return plain JSON instead of GraphQL).
Contributors

Full Changelog: graffle-js/graffle@7.3.5...7.4.0

v7.3.5

Compare Source

What's Changed

Full Changelog: graffle-js/graffle@v7.3.0...v7.3.5

v7.3.4

Compare Source

Bug Fixes
  • Fixed #​1281: GraphQL errors and data are now accessible from 4xx/5xx HTTP responses
  • Fixed #​1461: ClientError is properly returned for non-2xx responses with malformed bodies
  • Fixed #​1462: ClientError is properly returned for non-2xx responses with unsupported content types
Changes
  • Non-2xx HTTP responses now parse the response body first to extract GraphQL errors/data when available
  • Non-2xx responses with valid GraphQL bodies return ClientError with errors and data accessible
  • Non-2xx responses with invalid bodies still return ClientError (not generic Error) for backwards compatibility
  • This release reverts PRs #​1457 and #​1459 which introduced regressions, then reapplies a minimal fix for #​1281
Breaking Changes

None - this release maintains backwards compatibility while adding support for accessing GraphQL errors from 4xx/5xx responses.

v7.3.3

Compare Source

Bug Fixes
  • Non-JSON Error Response Handling: Fixed regression in 7.3.2 where servers returning HTTP 4xx/5xx status codes with non-JSON response bodies (HTML, plain text) would throw an unhelpful error: "Invalid execution result: result is not object or array" (#​1459, closes #​1458)
    • Added safe JSON parsing fallback for responses without proper Content-Type headers
    • Returns descriptive error messages with response body preview for non-JSON responses
    • Handles common production scenarios: load balancer errors (502/503 HTML pages), CDN errors, WAF/firewall responses, misconfigured servers
    • Maintains backward compatibility for servers that omit Content-Type but return valid JSON
    • Added comprehensive test coverage for HTML, plain text, and missing Content-Type scenarios
What Changed

Version 7.3.2 introduced a bug where the ELSE branch in parseResultFromResponse would pass raw strings (HTML, plain text) to a parser expecting objects/arrays. This only surfaced when:

  1. Server returns 4xx/5xx status code
  2. Content-Type header is missing or non-JSON (e.g., text/html, text/plain)
  3. Response body is not valid JSON

This is now fixed with graceful error handling and clear error messages.

v7.3.2

Compare Source

Bug Fixes

  • HTTP Error Handling: Fixed regression from v6 to v7 where HTTP 4xx/5xx responses would not include GraphQL errors from response body in ClientError (#​1457, closes #​1281)

    • Response body is now parsed before checking HTTP status
    • Users can access GraphQL errors via error.response.errors even with non-2xx status codes
    • Common use case: authentication errors (422), server errors (500)

  • graphql-codegen Compatibility: Added support for TypedDocumentString from @graphql-codegen when using documentMode: 'string' (#​1456, closes #​1453)

    • Handles boxed String objects created by TypedDocumentString class
    • Normalizes document input to prevent crashes when passing to GraphQL operations

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: (UTC)

  • 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

renovate Bot commented May 10, 2024 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: root@0.0.0
npm ERR! Found: typescript@7.0.2
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"7.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.3 <7" from ts-jest@29.4.15
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"29.4.15" 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/2026-10-26T23_01_21_453Z-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
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 16d579b to 1ae2b15 Compare November 10, 2025 18:54
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 1ae2b15 to 9bac2da Compare March 5, 2026 19:49
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 9bac2da to 3f4f55f Compare April 29, 2026 19:04
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 3f4f55f to c3db166 Compare September 7, 2026 23:22
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch 2 times, most recently from a738db5 to be1ae56 Compare October 1, 2026 05:16
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from be1ae56 to 1ab58c9 Compare October 5, 2026 18:11
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 1ab58c9 to 39af292 Compare October 20, 2026 18:49
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 39af292 to 0b521ef Compare October 26, 2026 23:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

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.

0 participants