Skip to content

Update dependency graphql-request to v7 - #1485

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

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

Conversation

@renovate

@renovaterenovateBot commented Apr 27, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeConfidence
graphql-request (source)6.1.07.4.0ageconfidence

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: (in timezone Asia/Shanghai)

  • Branch creation
    • "after 4am and before 8am on saturday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@zzdhybthuzzdhybthu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1

@renovate
renovateBotforce-pushed the renovate/graphql-request-7.x branch 5 times, most recently from dfa0d13 to c76e0dbCompareMay 2, 2025 23:13
@renovate
renovateBotforce-pushed the renovate/graphql-request-7.x branch 8 times, most recently from bcd7d55 to 2d34ccfCompareMay 11, 2025 14:59
@renovate
renovateBotforce-pushed the renovate/graphql-request-7.x branch 14 times, most recently from 0058298 to 57a79aaCompareMay 18, 2025 11:08
@renovate
renovateBotforce-pushed the renovate/graphql-request-7.x branch 9 times, most recently from bda5bb7 to 7ea6581CompareJune 6, 2025 23:09
@renovate
renovateBotforce-pushed the renovate/graphql-request-7.x branch 11 times, most recently from 28e712a to d5d5025CompareJune 13, 2025 23:11
@renovate
renovateBotforce-pushed the renovate/graphql-request-7.x branch 6 times, most recently from 6e7c1d3 to 17e0b38CompareJune 20, 2025 22:28
@renovate
renovateBotforce-pushed the renovate/graphql-request-7.x branch 3 times, most recently from 7f79498 to 42bec56CompareJune 27, 2025 11:53
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@zzdhybthu