Skip to content

chore: v14.0.0 release#3973

Open
kamilmysliwiec wants to merge 23 commits into
masterfrom
v14.0.0
Open

chore: v14.0.0 release#3973
kamilmysliwiec wants to merge 23 commits into
masterfrom
v14.0.0

Conversation

@kamilmysliwiec
Copy link
Copy Markdown
Member

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

niamu01 and others added 13 commits September 22, 2024 22:20
When subscriptions are configured with an explicit path (for example
`subscriptions: { 'graphql-ws': { path: '/graphql' } }`) alongside `useGlobalPrefix: true`,
the apollo driver previously passed that path straight through to GqlSubscriptionService
without prefixing it. The HTTP endpoint resolved to `/api/graphql` while the websocket
bound to `/graphql`, so client upgrades targeting the prefixed URL were rejected.

Apply the application's global prefix to user-supplied `graphql-ws` and
`subscriptions-transport-ws` paths in `mergeDefaultOptions`. Boolean shorthand
(`'graphql-ws': true`) is preserved as-is because the existing fall-through already uses
the prefixed `options.path`. Mercurius is unaffected because its subscription transport
reuses the mercurius route path which is already prefixed.

Closes #2477
…tional-dts

fix(@nestjs/graphql): keep resolvers required when skipping args
…lobal-prefix

fix(apollo): respect useGlobalPrefix on custom subscription path
…ed-fields

fix(graphql,apollo): ensures extensions are added to resolved fields
…nfo-nullable

fix(graphql): change info to nullable
…port-ws

Chore/remove subscriptions transport ws
kamilmysliwiec and others added 10 commits May 5, 2026 12:06
The build-time SDL emitted via autoSchemaFile in federation mode was
written using graphql's default printSchema, which strips @key, @external,
@extends, @requires and @provides. The runtime _service.sdl query was
unaffected. GraphQLSchemaBuilder.generateSchema now accepts an optional
printer; the federation factory passes printSchemaWithDirectives (subgraph
v2+) or printSubgraphSchema (v1), matching the existing runtime selection.

Closes #3722
# Conflicts:
#	packages/graphql/lib/schema-builder/factories/interface-definition.factory.ts
#	packages/graphql/lib/schema-builder/factories/object-type-definition.factory.ts
#	packages/graphql/lib/schema-builder/factories/union-definition.factory.ts
#	yarn.lock
@kamilmysliwiec kamilmysliwiec marked this pull request as ready for review May 14, 2026 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants