unstale

npm / @graphql-yoga/plugin-persisted-operations

@graphql-yoga/plugin-persisted-operations

What changed in @graphql-yoga/plugin-persisted-operations 3 to 4, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-13.

11 breaking1 new APIs and options

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

npx @unstale/cli init

@unstale/cli 0.3.0 on npm

@graphql-yoga/plugin-persisted-operations 47 changes

Breaking changes 6

  • Plugins added with addPlugin are inserted in place, so their hooks execute immediately after the plugin that added them.

    4.0.0upgrade guide

  • The minimum supported GraphQL version is now 16; GraphQL 14 and 15 are no longer supported.

    4.0.0release notes

  • Yoga now limits request bodies to 25,000,000 bytes by default. Set maxRequestBodySize: false in createYoga to disable the limit.

    4.0.0release notes

  • The minimum supported Node version is now 22; Node 18 and 20 are no longer supported.

    4.0.0release notes

  • Node.js v16 is no longer supported.

    3.0.0, 4.0.0upgrade guiderelease notes

  • Request body parsing is asynchronous, so yoga.fetch() can return a Promise where it previously returned a synchronous Response, even when resolvers and plugins are synchronous.

    4.0.0release notes

New APIs and options 1

  • The migration instructions install the graphql-yoga NPM package.

    4.0.0upgrade guide

@graphql-yoga/plugin-persisted-operations 35 changes

Breaking changes 5

  • This unused GraphiQL option was removed and can no longer be configured.

    3.0.0upgrade guide

  • This unused GraphiQL option was removed and can no longer be configured.

    3.0.0upgrade guide

  • Subscriptions now use GraphQL over SSE “distinct connections mode” instead of Yoga’s previous custom SSE transport; the notes recommend graphql-sse for clients.

    3.0.0upgrade guide

  • Subscriptions no longer support multipart/mixed as a transport method; they use text/event-stream instead.

    3.0.0upgrade guide

  • Parsing and validation caching are configured through this single option, replacing the separate parserCache and validationCache options.

    3.0.0upgrade guide