Skip to content

Bump graphiql from 5.4.0 to 6.0.1 in /juniper - #1423

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/juniper/graphiql-6.0.1
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/juniper/graphiql-6.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 10, 2026

Copy link
Copy Markdown
Contributor

Bumps graphiql from 5.4.0 to 6.0.1.

Release notes

Sourced from graphiql's releases.

graphiql@6.0.1

Patch Changes

  • #4757 bb80494 Thanks @​trevor-scheer! - Remove the response pane's Tree view. JSON and Table views remain available. A saved Tree preference falls back to JSON. The exported ResponseView type now accepts only 'json' and 'table'.
  • Updated dependencies [bb80494]:
    • @​graphiql/react@​1.0.2

graphiql@6.0.0

Major Changes

  • #4478 066528a Thanks @​trevor-scheer! - GraphQL.js 15 and 16.0–16.10 are no longer supported peer dependencies. The supported range is ^16.11.0 || ^17.0.0. GraphQL.js 16.11 fixes OneOf input validation for nullable variables and tightens input-object coercion to reject arrays, giving GraphiQL 6 a correct baseline for OneOf inputs. Upgrade graphql before upgrading these packages.

  • #4416 9c153e2 Thanks @​trevor-scheer! - Replace @graphiql/plugin-explorer with @graphiql/plugin-query-builder. Remove the Explorer dependency and plugin registration when upgrading. Query Builder is included in GraphiQL's default plugin set; if you supply a custom plugins array, add QUERY_BUILDER_PLUGIN from graphiql to retain query-building support.

  • #4566 f916fd6 Thanks @​trevor-scheer! - Upgrade the bundled Monaco Editor to 0.57 and adopt the worker and ESM entry points introduced in 0.56. Published packages accept monaco-editor >=0.56.0 <0.58.0. If you configure Monaco directly, use Monaco 0.56 or 0.57, replace monaco-editor/esm/vs/* imports with exported entry points, and configure MonacoEnvironment.getWorker to return the GraphQL worker for the graphql label. Custom GraphQL workers must initialize immediately and provide non-cloneable configuration by overriding GraphQLWorker.initialize. GraphiQL's worker setup helpers handle these changes and load the matching monaco-graphql major. See the GraphiQL 6 migration guide for examples. This update builds on the initial worker migration contributed by @​lukasbash.

  • #4610 b40d7fe Thanks @​trevor-scheer! - Remove the operationName prop from GraphiQL and GraphiQLProvider. Each request now uses the operation selected in the active tab. Use the cursor, Run picker, or useGraphiQLActions().setOperationName(name) to select an operation; onEditOperationName still reports selection changes.

  • #4425 ff2e4ca Thanks @​trevor-scheer! - Remove the composable GraphiQL.Toolbar and GraphiQL.Logo slots. Editor actions are now contributed through a plugin's sessionActions, and branding is customized through the brand prop passed to <GraphiQL> (or <TopBar> directly). GraphiQL.Footer is unchanged. See the Toolbar and Logo migration guide for before/after examples.

  • #4333 093cb10 Thanks @​trevor-scheer! - Add createTransport and a structured Transport API for queries, mutations, subscriptions, and incremental delivery. Pass a transport through <GraphiQL transport={...}>; the transport and fetcher props are mutually exclusive at the type level.

    GraphiQLProps is now a union. If a TypeScript wrapper uses interface AppProps extends GraphiQLProps, replace it with a type intersection such as type AppProps = GraphiQLProps & { applicationName: string }, even when retaining fetcher. See the migration overview.

    When supportedMethods is omitted, createTransport discovers endpoint capabilities through OPTIONS and the Allow header. Queries prefer QUERY, then POST, then GET. Mutations and operations of unknown type require POST. An explicit method override applies to queries and fails if the endpoint excludes it. GET sends GraphQL parameters in the URL; POST and QUERY send a JSON body.

    Discovery is shared by concurrent requests and repeats when effective request headers change. If discovery fails, exceeds two seconds, or the Allow header is missing or malformed, the transport assumes only its initially configured method (POST by default) is available. A valid advertisement containing no supported methods blocks execution. Pass a nonempty supportedMethods array to skip discovery for known capabilities. Cross-origin servers must permit OPTIONS and expose Allow through Access-Control-Expose-Headers.

    TransportResponse exposes HTTP method, status, headers, timing, and byte sizes alongside the GraphQL result. HTTP metadata remains available when a response body is not valid JSON. Its ok field accounts for both HTTP status and GraphQL errors. TransportRequest supports GraphQL extensions and an abort signal. Subscriptions require an explicit subscriptionClient with an iterate(request) method, supported by graphql-ws v6 and graphql-sse clients.

    Plugins can transform outgoing requests with onBeforeSend and observe responses or request failures with onResponse and onError, available through useGraphiQLPluginContext().transport. Each registration returns a cleanup function. This context field is absent when using the legacy fetcher prop.

    Transports can expose query method preferences through optional setMethod, methodOverride, and subscribe(listener) APIs. Calling setMethod() without an argument restores automatic selection. methodOverride distinguishes an explicit preference from Auto; Transport.method reflects the query method, while TransportResponse.method reports the method actually used for an execution. subscribe(listener) notifies GraphiQL of preference and capability changes and returns an unsubscribe function. These notifications are independent of request lifecycle hooks. createTransport implements these APIs; custom transports can omit them.

    createGraphiQLFetcher, Fetcher, and <GraphiQL fetcher={...}> are deprecated but remain supported. See the Transport migration guide for examples and custom transport requirements.

  • #4228 Thanks @​trevor-scheer! - Redesign GraphiQL with light and dark themes, an endpoint and Run bar, a plugin activity rail, a resizable side panel, a status bar, and a Variables/Headers tab strip. The Documentation Explorer, History, and Monaco editor themes follow the same design. Settings offer theme, density, and font-size controls.

    The top bar joins Run/Stop with the selected operation name, its QRY/MUT/SUB label, and an HTTP method selector. Selecting an operation does not execute it; use Run or the keyboard shortcut. The method menu offers Auto for queries and explains unavailable options. Selected rows use the GraphQL logo pink, while keyboard focus has a separate outline.

    The response pane adds HTTP method, status, timing, and size from transports that provide them, a copy action, and persisted JSON, Tree, and Table views. Tree expands response objects and arrays; Table presents each list field separately. Saved operations show when they have unsaved edits, and tabs with multiple operations identify the active operation.

    Improve keyboard focus visibility and screen-reader labels throughout the interface. Escape cancels History label edits and returns focus to the edit button. Closing Settings returns focus to its trigger.

    Unify GraphQL syntax coloring across Documentation Explorer, History, and Query Builder. Use the --type-scalar, --type-enum, --type-input, and --type-composite CSS tokens and the exported typeCategory helper to customize type-category colors.

    The design tokens use OKLCH colors, and the build targets the defaults browserslist preset. The v5 --color-* variables remain defined but no longer theme the built-in UI; migrate existing overrides to the new OKLCH tokens. Custom CSS that overrides internal class names may also need updating. See CSS and retheming for migration guidance. Refs graphql/graphiql#4219.

Minor Changes

... (truncated)

Changelog

Sourced from graphiql's changelog.

6.0.1

Patch Changes

  • #4757 bb80494 Thanks @​trevor-scheer! - Remove the response pane's Tree view. JSON and Table views remain available. A saved Tree preference falls back to JSON. The exported ResponseView type now accepts only 'json' and 'table'.
  • Updated dependencies [bb80494]:
    • @​graphiql/react@​1.0.2

6.0.0

Major Changes

  • #4478 066528a Thanks @​trevor-scheer! - GraphQL.js 15 and 16.0–16.10 are no longer supported peer dependencies. The supported range is ^16.11.0 || ^17.0.0. GraphQL.js 16.11 fixes OneOf input validation for nullable variables and tightens input-object coercion to reject arrays, giving GraphiQL 6 a correct baseline for OneOf inputs. Upgrade graphql before upgrading these packages.

  • #4416 9c153e2 Thanks @​trevor-scheer! - Replace @graphiql/plugin-explorer with @graphiql/plugin-query-builder. Remove the Explorer dependency and plugin registration when upgrading. Query Builder is included in GraphiQL's default plugin set; if you supply a custom plugins array, add QUERY_BUILDER_PLUGIN from graphiql to retain query-building support.

  • #4566 f916fd6 Thanks @​trevor-scheer! - Upgrade the bundled Monaco Editor to 0.57 and adopt the worker and ESM entry points introduced in 0.56. Published packages accept monaco-editor >=0.56.0 <0.58.0. If you configure Monaco directly, use Monaco 0.56 or 0.57, replace monaco-editor/esm/vs/* imports with exported entry points, and configure MonacoEnvironment.getWorker to return the GraphQL worker for the graphql label. Custom GraphQL workers must initialize immediately and provide non-cloneable configuration by overriding GraphQLWorker.initialize. GraphiQL's worker setup helpers handle these changes and load the matching monaco-graphql major. See the GraphiQL 6 migration guide for examples. This update builds on the initial worker migration contributed by @​lukasbash.

  • #4610 b40d7fe Thanks @​trevor-scheer! - Remove the operationName prop from GraphiQL and GraphiQLProvider. Each request now uses the operation selected in the active tab. Use the cursor, Run picker, or useGraphiQLActions().setOperationName(name) to select an operation; onEditOperationName still reports selection changes.

  • #4425 ff2e4ca Thanks @​trevor-scheer! - Remove the composable GraphiQL.Toolbar and GraphiQL.Logo slots. Editor actions are now contributed through a plugin's sessionActions, and branding is customized through the brand prop passed to <GraphiQL> (or <TopBar> directly). GraphiQL.Footer is unchanged. See the Toolbar and Logo migration guide for before/after examples.

  • #4333 093cb10 Thanks @​trevor-scheer! - Add createTransport and a structured Transport API for queries, mutations, subscriptions, and incremental delivery. Pass a transport through <GraphiQL transport={...}>; the transport and fetcher props are mutually exclusive at the type level.

    GraphiQLProps is now a union. If a TypeScript wrapper uses interface AppProps extends GraphiQLProps, replace it with a type intersection such as type AppProps = GraphiQLProps & { applicationName: string }, even when retaining fetcher. See the migration overview.

    When supportedMethods is omitted, createTransport discovers endpoint capabilities through OPTIONS and the Allow header. Queries prefer QUERY, then POST, then GET. Mutations and operations of unknown type require POST. An explicit method override applies to queries and fails if the endpoint excludes it. GET sends GraphQL parameters in the URL; POST and QUERY send a JSON body.

    Discovery is shared by concurrent requests and repeats when effective request headers change. If discovery fails, exceeds two seconds, or the Allow header is missing or malformed, the transport assumes only its initially configured method (POST by default) is available. A valid advertisement containing no supported methods blocks execution. Pass a nonempty supportedMethods array to skip discovery for known capabilities. Cross-origin servers must permit OPTIONS and expose Allow through Access-Control-Expose-Headers.

    TransportResponse exposes HTTP method, status, headers, timing, and byte sizes alongside the GraphQL result. HTTP metadata remains available when a response body is not valid JSON. Its ok field accounts for both HTTP status and GraphQL errors. TransportRequest supports GraphQL extensions and an abort signal. Subscriptions require an explicit subscriptionClient with an iterate(request) method, supported by graphql-ws v6 and graphql-sse clients.

    Plugins can transform outgoing requests with onBeforeSend and observe responses or request failures with onResponse and onError, available through useGraphiQLPluginContext().transport. Each registration returns a cleanup function. This context field is absent when using the legacy fetcher prop.

    Transports can expose query method preferences through optional setMethod, methodOverride, and subscribe(listener) APIs. Calling setMethod() without an argument restores automatic selection. methodOverride distinguishes an explicit preference from Auto; Transport.method reflects the query method, while TransportResponse.method reports the method actually used for an execution. subscribe(listener) notifies GraphiQL of preference and capability changes and returns an unsubscribe function. These notifications are independent of request lifecycle hooks. createTransport implements these APIs; custom transports can omit them.

    createGraphiQLFetcher, Fetcher, and <GraphiQL fetcher={...}> are deprecated but remain supported. See the Transport migration guide for examples and custom transport requirements.

  • #4228 Thanks @​trevor-scheer! - Redesign GraphiQL with light and dark themes, an endpoint and Run bar, a plugin activity rail, a resizable side panel, a status bar, and a Variables/Headers tab strip. The Documentation Explorer, History, and Monaco editor themes follow the same design. Settings offer theme, density, and font-size controls.

    The top bar joins Run/Stop with the selected operation name, its QRY/MUT/SUB label, and an HTTP method selector. Selecting an operation does not execute it; use Run or the keyboard shortcut. The method menu offers Auto for queries and explains unavailable options. Selected rows use the GraphQL logo pink, while keyboard focus has a separate outline.

    The response pane adds HTTP method, status, timing, and size from transports that provide them, a copy action, and persisted JSON, Tree, and Table views. Tree expands response objects and arrays; Table presents each list field separately. Saved operations show when they have unsaved edits, and tabs with multiple operations identify the active operation.

    Improve keyboard focus visibility and screen-reader labels throughout the interface. Escape cancels History label edits and returns focus to the edit button. Closing Settings returns focus to its trigger.

    Unify GraphQL syntax coloring across Documentation Explorer, History, and Query Builder. Use the --type-scalar, --type-enum, --type-input, and --type-composite CSS tokens and the exported typeCategory helper to customize type-category colors.

    The design tokens use OKLCH colors, and the build targets the defaults browserslist preset. The v5 --color-* variables remain defined but no longer theme the built-in UI; migrate existing overrides to the new OKLCH tokens. Custom CSS that overrides internal class names may also need updating. See CSS and retheming for migration guidance. Refs graphql/graphiql#4219.

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [graphiql](https://github.com/graphql/graphiql/tree/HEAD/packages/graphiql) from 5.4.0 to 6.0.1.
- [Release notes](https://github.com/graphql/graphiql/releases)
- [Changelog](https://github.com/graphql/graphiql/blob/main/packages/graphiql/CHANGELOG.md)
- [Commits](https://github.com/graphql/graphiql/commits/graphiql@6.0.1/packages/graphiql)

---
updated-dependencies:
- dependency-name: graphiql
  dependency-version: 6.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added enhancement Improvement of existing features or bugfix javascript Related to Javascript specifically k::dependencies Pull requests that update a dependency file k::integration Related to integration with third-party libraries or systems labels Nov 10, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Improvement of existing features or bugfix javascript Related to Javascript specifically k::dependencies Pull requests that update a dependency file k::integration Related to integration with third-party libraries or systems

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants