Support NestJS v12 / @nestjs/graphql v14 peer dependencies in @graphql-yoga/nestjs

Is your feature request related to a problem? Please describe.

NestJS v12 has been released, with all official packages shipping as ESM (@nestjs/core, @nestjs/common, etc.), and @nestjs/graphql@14 already targets it — its peerDependencies require @nestjs/core: ^12.0.0 and @nestjs/common: ^12.0.0.

However, the latest @graphql-yoga/nestjs (3.24.0, published 2026-09-11, after v12 shipped) still declares:

"@nestjs/core": "^11.0.0",
"@nestjs/common": "^11.0.0",
"@nestjs/graphql": "^13.0.0"

This means a project that wants to adopt NestJS v12 (for the ESM-first packaging) while keeping the Yoga driver — instead of switching to Apollo or Mercurius — currently can't do so without forcing an incompatible peer dependency combination.

I checked the Dependency Dashboard (#1725) and recent PRs in this repo and didn't see anything in progress towards this bump, so opening this to track it.

Describe the solution you'd like

Bump @graphql-yoga/nestjs's peer dependencies to accept @nestjs/core@^12.0.0, @nestjs/common@^12.0.0 and @nestjs/graphql@^14.0.0 (ideally keeping v11 support too, if that's feasible), and verify the driver still works correctly given the lifecycle-hook ordering changes introduced in Nest v12.

Describe alternatives you've considered

• Staying on @nestjs/core@^11 / @nestjs/graphql@^13, which works today but forgoes the ESM-first packaging v12 provides.
• Forcing the peer dependency mismatch (--legacy-peer-deps / overrides), which is untested by the maintainers and risky given the v12 lifecycle-hook changes.

Additional context

Happy to help test a release candidate against a real schema-first project if that's useful.