Skip to content

Update dependency graphql-request to v7 - #1365

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

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

Conversation

@renovate

@renovate renovate Bot commented Jun 27, 2024

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
graphql-request (source) 6.1.07.4.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.

@vercel

vercel Bot commented Jun 27, 2024

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
ramble Ignored Ignored Preview Aug 26, 2026 1:17pm

Request Review

@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from ddb028f to a0c3e3c Compare July 10, 2024 19:22
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from a0c3e3c to 347d326 Compare August 15, 2024 06:17
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 347d326 to db44b37 Compare August 22, 2024 00:39
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from db44b37 to e8441ea Compare August 27, 2024 22:42
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from e8441ea to 067816b Compare September 5, 2024 02:01
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 067816b to 12356a5 Compare September 10, 2024 00:19
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 12356a5 to 0b4cee2 Compare September 12, 2024 00:54
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 0b4cee2 to 3f68f4d Compare September 12, 2024 22:44
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 3f68f4d to e6c77e5 Compare September 17, 2024 23:24
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from e6c77e5 to 79f51d7 Compare September 25, 2024 22:54
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 79f51d7 to a8408f9 Compare October 7, 2024 19:51
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from a8408f9 to af3b411 Compare November 1, 2024 18:05
@coderabbitai

coderabbitai Bot commented Nov 1, 2024

Copy link
Copy Markdown

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.


Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from fe10f83 to acaffeb Compare August 31, 2025 14:38
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from acaffeb to 2cd8c2d Compare September 25, 2025 18:38
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 2cd8c2d to fca83a8 Compare October 15, 2025 05:05
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from fca83a8 to 3799890 Compare October 18, 2025 21:45
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 3799890 to f4d5b8d Compare November 9, 2025 17:38
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from f4d5b8d to 443cab5 Compare November 10, 2025 21:40
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 443cab5 to 3c05f63 Compare November 11, 2025 04:31
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 3c05f63 to 436430a Compare November 18, 2025 15:01
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 436430a to ff39218 Compare November 25, 2025 18:38
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from ff39218 to 812802d Compare December 12, 2025 17:51
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 812802d to 7be16fc Compare December 31, 2025 16:12
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 7be16fc to 71337ea Compare February 12, 2026 13:14
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 71337ea to cc63b93 Compare April 29, 2026 16:17
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from cc63b93 to 3a7e80b Compare July 17, 2026 16:59
@renovate
renovate Bot force-pushed the renovate/graphql-request-7.x branch from 3a7e80b to c28776f Compare August 26, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants