unstale

npm / @graphql-tools/utils

@graphql-tools/utils

What changed in @graphql-tools/utils 12 to 13, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-20.

1 security8 new APIs and options1 behavior and defaults1 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli on npm

@graphql-tools/utils 1310 changes

New APIs and options 8

  • A helper for getting the default incremental delivery spec.

    13.1.1release notes

  • A helper for getting incremental spec parameter names.

    13.1.1release notes

  • A helper for getting the multipart content type.

    13.1.1release notes

  • Provides a shared HTTP contract mapping Accept and Content-Type parameters to executor payload IDs, so servers can look up spec strings instead of hardcoding them.

    13.1.1release notes

  • A helper for looking up an incremental delivery spec.

    13.1.1release notes

  • Pass incrementalSpec as 'v0.1' or 'v0.2' on execute, subscribe, normalizedExecutor, or ExecutionRequest to select the incremental delivery payload format; 'v0.1' remains the default.

    13.1.0release notes

  • Adds a helper for GraphQL 16/17 VariableValues compatibility when calling getArgumentValues.

    13.0.2release notes

  • Adds a helper to normalize getVariableValues results for GraphQL 16/17 VariableValues compatibility.

    13.0.2release notes

Behavior and default changes 1

  • Supports merging v0.2 payloads by tracking pending ids, placing deferred data and streamed items, and folding completed errors into errors.

    13.1.0release notes

Fixes and other changes 1

  • Flattens nested deferred patches so result visiting sees fields under a child @defer.

    13.1.0release notes

@graphql-tools/utils 121 changes

Security 1

  • GraphQL Tools has prototype pollution in well-established utility function mergeDeep

    12.0.1security advisory