FAQ | This is a LIVE service | Changelog

fix(deps): update all non-major dependencies

This MR contains the following updates:

Package Change Age Confidence
@mui/x-date-pickers (source) 7.29.1 -> 7.29.4 age confidence
@types/node (source) 24.10.0 -> 24.10.1 age confidence
@types/react (source) 19.2.2 -> 19.2.3 age confidence
@types/react-dom (source) 19.2.2 -> 19.2.3 age confidence
graphql-request (source) 7.3.1 -> 7.3.3 age confidence

Release Notes

mui/mui-x (@​mui/x-date-pickers)

v7.29.4

Compare Source

We'd like to offer a big thanks to the 6 contributors who made this release possible. Here are some highlights :

  • 🐞 Bugfixes

Special thanks go out to the community members for their valuable contributions: @​campmarc, @​whereisrmsqhs, @​jyash97

Following are all team members who have contributed to this release: @​mapache-salvaje, @​cherniavskii, @​noraleonte.

Data Grid
@mui/x-data-grid@7.29.4
@mui/x-data-grid-pro@7.29.4 pro

Same changes as in @mui/x-data-grid@7.29.4, plus:

@mui/x-data-grid-premium@7.29.4 premium

Same changes as in @mui/x-data-grid-pro@7.29.4.

Date and Time Pickers
@mui/x-date-pickers@7.29.4
@mui/x-date-pickers-pro@7.29.4 pro

Same changes as in @mui/x-date-pickers@7.29.4.

Docs

v7.29.3

Compare Source

We'd like to offer a big thanks to the 3 contributors who made this release possible. Here are some highlights :

  • 🐞 Bugfixes

Team members who have contributed to this release: @​arminmeh, @​LukasTy, and @​MBilalShafi.

Data Grid
@mui/x-data-grid@7.29.3
@mui/x-data-grid-pro@7.29.3 pro

Same changes as in @mui/x-data-grid@7.29.3.

@mui/x-data-grid-premium@7.29.3 premium

Same changes as in @mui/x-data-grid-pro@7.29.3.

Date and Time Pickers
@mui/x-date-pickers@7.29.3
@mui/x-date-pickers-pro@7.29.3 pro

Same changes as in @mui/x-date-pickers@7.29.3.

v7.29.2

Compare Source

We'd like to offer a big thanks to the 7 contributors who made this release possible. Here are some highlights :

  • 🌍 Add Armenian (hy-AM) locale on the Data Grid
  • 🌍 Improve Italian (it-IT) locale on the Date and Time Pickers
  • 🐞 Bugfixes

Special thanks go out to the community contributors who have helped make this release possible: @​ArturAghakaryan, @​federico-ntr.

Following are all team members who have contributed to this release: @​arminmeh, @​JCQuintas, @​KenanYusuf, @​MBilalShafi, @​oliviertassinari.

Data Grid
@mui/x-data-grid@7.29.2
@mui/x-data-grid-pro@7.29.2 pro

Same changes as in @mui/x-data-grid@7.29.2.

@mui/x-data-grid-premium@7.29.2 premium

Same changes as in @mui/x-data-grid-pro@7.29.2.

Date and Time Pickers
@mui/x-date-pickers@7.29.2
@mui/x-date-pickers-pro@7.29.2 pro

Same changes as in @mui/x-date-pickers@7.29.2.

Docs
Core
graffle-js/graffle (graphql-request)

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

Configuration

📅 Schedule: Branch creation - Monday through Friday ( * * * * 1-5 ) in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited by uis-devops-renovatebot

Merge request reports

Loading