Version Packages

[github-actions]

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@5.3.0

Minor Changes

• #4448 e751f65 Thanks @dargmuesli! - Add customScalarSchemas prop to GraphiQLProvider/GraphiQL, forwarded to monaco-graphql's per-schema customScalarSchemas config. Without it, the variable editor's live JSON Schema linter assumes every custom scalar only accepts primitives (string, number, boolean, integer) and reports a spurious "Incorrect type" error for scalars that legitimately accept objects or arrays (e.g. a JSON or GeoJSON scalar). graphql-language-service and monaco-graphql already supported this per-scalar override; @graphiql/react just never exposed it.

Patch Changes

• Updated dependencies [6090495, e751f65]:
  • @graphiql/react@0.38.0
  • @graphiql/plugin-doc-explorer@0.4.3
  • @graphiql/plugin-history@0.4.3

@graphiql/react@0.38.0

Minor Changes

• #4448 e751f65 Thanks @dargmuesli! - Add customScalarSchemas prop to GraphiQLProvider/GraphiQL, forwarded to monaco-graphql's per-schema customScalarSchemas config. Without it, the variable editor's live JSON Schema linter assumes every custom scalar only accepts primitives (string, number, boolean, integer) and reports a spurious "Incorrect type" error for scalars that legitimately accept objects or arrays (e.g. a JSON or GeoJSON scalar). graphql-language-service and monaco-graphql already supported this per-scalar override; @graphiql/react just never exposed it.

Patch Changes

• #4430 6090495 Thanks @trevor-scheer! - Disable Fira Code's font ligatures in the Monaco editors. Programming ligatures rewrote valid GraphQL into misleading glyphs — most notably Int!=1 (a non-null Int with a default value of 1) rendered as Int≠1, implying an inequality that isn't there. Characters now render literally. The Windows caret fix from #4040 is preserved.

@graphiql/plugin-code-exporter@5.1.3

Patch Changes

• Updated dependencies [6090495, e751f65]:
  • @graphiql/react@0.38.0

@graphiql/plugin-doc-explorer@0.4.3

Patch Changes

• Updated dependencies [6090495, e751f65]:
  • @graphiql/react@0.38.0

@graphiql/plugin-explorer@5.1.4

Patch Changes

• Updated dependencies [6090495, e751f65]:
  • @graphiql/react@0.38.0

@graphiql/plugin-history@0.4.3

Patch Changes

• Updated dependencies [6090495, e751f65]:
  • @graphiql/react@0.38.0

vscode-graphql-syntax@1.3.12

Patch Changes

• #4385 bd73a95 Thanks @glen-84! - Highlight GraphQL string values — including single-line and block (triple-quoted) strings in directive and field arguments, list items, and default values — as strings instead of comments. Descriptions are now scoped as documentation (comment.block.documentation / comment.line.documentation) so themes can style them distinctly while still defaulting to comment colors.