Skip to content

fix(deps): update dependency graphql-request to v7 #1519

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
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update dependency graphql-request to v7 #1519

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 9, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
graphql-request (source) 6.1.0 → 7.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: Branch creation - "after 10pm every weekday,before 5am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).

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

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

@cypress
Copy link

cypress bot commented Aug 9, 2024 •
edited
Loading

BanManager-WebUI    Run #9435

Run Properties:  status check failed Failed #9435  •  git commit 116272bbb2 ℹ️: Merge e32c5e2ac6be17eba449d59a6a97b97ec524cca2 into b4af94862d2b3b57e869a07e3977...
Project BanManager-WebUI
Branch Review renovate/graphql-request-7.x
Run status status check failed Failed #9435
Run duration 01m 26s
Commit git commit 116272bbb2 ℹ️: Merge e32c5e2ac6be17eba449d59a6a97b97ec524cca2 into b4af94862d2b3b57e869a07e3977...
Committer renovate[bot]
View all properties for this run ↗︎
Test results
Tests that failed  Failures 13
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 1
Tests that did not run due to a failure in a mocha hook  Skipped 4
Tests that passed  Passing 8
View all changes introduced in this branch ↗︎

Tests for review

Failed  account/email.spec.js • 3 failed tests

View Output

Test Artifacts
Account/Email > errors if incorrect current password Test Replay Screenshots
Account/Email > errors email used Test Replay Screenshots
Account/Email > successfully changes email Test Replay Screenshots
Failed  account/password.spec.js • 3 failed tests

View Output

Test Artifacts
Account/Password > errors if incorrect current password Test Replay Screenshots
Account/Password > errors if new password weak Test Replay Screenshots
Account/Password > successfully changes password Test Replay Screenshots
Failed  documents.spec.js • 6 failed tests

View Output

Test Artifacts
Document Uploads > File Selection > uploads file via attach button Test Replay Screenshots
Document Uploads > Drag and Drop > shows drop zone highlight on drag enter Test Replay Screenshots
Document Uploads > Paste Upload > uploads image pasted into textarea Test Replay Screenshots
Document Uploads > File Removal > removes uploaded file from form Test Replay Screenshots
Document Uploads > Error Handling > rejects invalid file types Test Replay Screenshots
Document Uploads > Document Deletion (After Submission) > creates appeal with documents and can delete them Test Replay Screenshots
Failed  login.spec.js • 1 failed test

View Output

Test Artifacts
Login > logs in via email Test Replay Screenshots

@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 6 times, most recently from 0102f19 to 6e41f44 Compare August 16, 2024 06:34
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 6e41f44 to f5f856f Compare August 18, 2024 03:10
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 9 times, most recently from ab351e6 to b10d007 Compare September 24, 2024 06:20
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 8 times, most recently from 5a18500 to ae270a5 Compare September 30, 2024 07:41
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 5 times, most recently from 4e021d7 to d30ee4a Compare October 4, 2024 04:19
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 5 times, most recently from 3ad97d5 to 363c4ba Compare December 15, 2025 17:32
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 16 times, most recently from 5dc65ef to d05333d Compare December 23, 2025 13:46
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch 7 times, most recently from aeb71b2 to 8ff4868 Compare December 31, 2025 15:38
@renovate renovate bot force-pushed the renovate/graphql-request-7.x branch from 8ff4868 to e32c5e2 Compare December 31, 2025 19:41
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant