This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@graphiql/toolkit@0.12.0

Minor Changes

• #4199 463df14 Thanks @trevor-scheer! - Send spec-compliant Accept header (application/graphql-response+json) in createSimpleFetcher

codemirror-graphql@2.2.5

Patch Changes

• Updated dependencies [914a547, 10f66d5]:
  • graphql-language-service@5.5.1

graphiql@5.2.3

Patch Changes

• #4181 f1a210e Thanks @trevor-scheer! - Fix schema prop to skip introspection when IntrospectionQuery data is provided

  Previously, passing an IntrospectionQuery result as the schema prop would still trigger a network introspection request. The shouldIntrospect check only recognized GraphQLSchema instances (via isSchema), not raw introspection data. Now, when an IntrospectionQuery is passed, a schema is built from it directly using buildClientSchema and introspection is skipped.

• #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

• Updated dependencies [f1a210e, 6f5d5d2, 40359eb, e7b30c1]:

  • @graphiql/react@0.37.4
  • @graphiql/plugin-doc-explorer@0.4.2
  • @graphiql/plugin-history@0.4.2

@graphiql/plugin-code-exporter@5.1.2

Patch Changes

• #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

@graphiql/plugin-doc-explorer@0.4.2

Patch Changes

• #4231 6f5d5d2 Thanks @trevor-scheer! - Fix degraded type declarations in published packages

  Both packages import from @graphiql/react at build time but only declared it as a peer dependency. Yarn workspaces topologically orders builds via dependencies/devDependencies, not peerDependencies, so on a clean checkout these plugins built before @graphiql/react had emitted its dist/*.d.ts. vite-plugin-dts then ran tsc against unresolved @graphiql/react imports, fell back to any for any return type that flowed through useGraphiQL, and published .d.ts artifacts where hooks like useDocExplorer and useDocExplorerActions resolved to () => any instead of their real shapes.

  Adding @graphiql/react as a devDependency matches the pattern already in @graphiql/plugin-explorer and @graphiql/plugin-code-exporter and lets the build run in topological order.

• #4140 40359eb Thanks @trevor-scheer! - Remove react-compiler-runtime peer dependency

• #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

@graphiql/plugin-explorer@5.1.2

Patch Changes

• #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

@graphiql/plugin-history@0.4.2

Patch Changes

• #4231 6f5d5d2 Thanks @trevor-scheer! - Fix degraded type declarations in published packages

  Both packages import from @graphiql/react at build time but only declared it as a peer dependency. Yarn workspaces topologically orders builds via dependencies/devDependencies, not peerDependencies, so on a clean checkout these plugins built before @graphiql/react had emitted its dist/*.d.ts. vite-plugin-dts then ran tsc against unresolved @graphiql/react imports, fell back to any for any return type that flowed through useGraphiQL, and published .d.ts artifacts where hooks like useDocExplorer and useDocExplorerActions resolved to () => any instead of their real shapes.

  Adding @graphiql/react as a devDependency matches the pattern already in @graphiql/plugin-explorer and @graphiql/plugin-code-exporter and lets the build run in topological order.

• #4140 40359eb Thanks @trevor-scheer! - Remove react-compiler-runtime peer dependency

• #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

• Updated dependencies [463df14]:

  • @graphiql/toolkit@0.12.0

@graphiql/react@0.37.4

Patch Changes

• #4181 f1a210e Thanks @trevor-scheer! - Fix schema prop to skip introspection when IntrospectionQuery data is provided

  Previously, passing an IntrospectionQuery result as the schema prop would still trigger a network introspection request. The shouldIntrospect check only recognized GraphQLSchema instances (via isSchema), not raw introspection data. Now, when an IntrospectionQuery is passed, a schema is built from it directly using buildClientSchema and introspection is skipped.

• #4140 40359eb Thanks @trevor-scheer! - Remove react-compiler-runtime peer dependency

• #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

• Updated dependencies [914a547, 463df14, 4bb7909, 10f66d5]:

  • graphql-language-service@5.5.1
  • @graphiql/toolkit@0.12.0
  • monaco-graphql@1.7.4

graphql-language-service@5.5.1

Patch Changes

• #3882 914a547 Thanks @bensengupta! - Fix off-by-one when hovering over token

• #4222 10f66d5 Thanks @trevor-scheer! - Unpin and update graphql-config dependency

graphql-language-service-server@2.14.9

Patch Changes

• #4187 ca83879 Thanks @trevor-scheer! - Bump required TypeScript runtime dependency from ^5.3.3 to ^5.8.0. This is preparatory work for adopting the TypeScript Native Preview (tsgo) compiler in a follow-up change, which tracks TypeScript 5.8 semantics. In practice ^5.3.3 already resolved to TS 5.8+ for most consumers; the new floor only affects consumers who pin TypeScript to 5.3–5.7 via resolutions or overrides.

• #4222 10f66d5 Thanks @trevor-scheer! - Unpin and update graphql-config dependency

• Updated dependencies [914a547, 10f66d5]:

  • graphql-language-service@5.5.1

monaco-graphql@1.7.4

Patch Changes

• #4225 4bb7909 Thanks @trevor-scheer! - Fix hover crashing on the first line of a query

  GraphQLWorker.doHover was passing 0-indexed positions to getRange, which expects a 1-indexed SourceLocation (per the GraphQL spec). On the first line this caused Expected Parser stream to be available to be logged and hover to return null. On other lines it returned the range of the previous line's last token rather than the token under the cursor. Use getTokenAtPosition to compute the actual token range instead.

• Updated dependencies [914a547, 10f66d5]:

  • graphql-language-service@5.5.1

vscode-graphql@0.13.3

Patch Changes

• #4183 2ef9389 Thanks @trevor-scheer! - Fix VS Code extension publishing scripts

• Updated dependencies [ca83879, 10f66d5]:

  • graphql-language-service-server@2.14.9

vscode-graphql-execution@0.3.3

Patch Changes

• #4183 2ef9389 Thanks @trevor-scheer! - Fix VS Code extension publishing scripts

• #4222 10f66d5 Thanks @trevor-scheer! - Unpin and update graphql-config dependency

vscode-graphql-syntax@1.3.9

Patch Changes

• #4183 2ef9389 Thanks @trevor-scheer! - Fix VS Code extension publishing scripts

• #4143 7979bf5 Thanks @Netail! - Add syntax highlighting support for subscription operations.

• #4144 f7e2a56 Thanks @jsmnbom! - Add text.html.vue as inline injection target.

  This PR broke tooling by changing the vue grammar scope from source.vue to text.html.vue. This adds text.html.vue as an additional injection target for GraphQL syntax highlighting so that it works in both cases.