Repository navigation
chore(deps): update nest-graphql monorepo to v14.2.0 - #8
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/nest-graphql-monorepo
branch
26 times, most recently
from
October 10, 2026 16:25
f9beab6 to
448a890
Compare
renovate
Bot
force-pushed
the
renovate/nest-graphql-monorepo
branch
4 times, most recently
from
October 13, 2026 04:27
b3c7017 to
afbb820
Compare
renovate
Bot
force-pushed
the
renovate/nest-graphql-monorepo
branch
4 times, most recently
from
October 27, 2026 12:27
38a4b3c to
e9087b8
Compare
renovate
Bot
force-pushed
the
renovate/nest-graphql-monorepo
branch
8 times, most recently
from
November 2, 2026 12:51
b816f5b to
0d823b8
Compare
renovate
Bot
force-pushed
the
renovate/nest-graphql-monorepo
branch
5 times, most recently
from
November 4, 2026 19:04
a231f31 to
1ab9739
Compare
renovate
Bot
force-pushed
the
renovate/nest-graphql-monorepo
branch
9 times, most recently
from
November 6, 2026 08:04
4ea9fb4 to
b852a11
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
14.0.1→14.2.014.0.1→14.2.0Release Notes
nestjs/graphql (@nestjs/apollo)
v14.2.0Compare Source
This release fixes several security issues and a range of correctness bugs in schema generation, resolver binding and the drivers. Upgrading is recommended for all users of
@nestjs/graphql,@nestjs/apolloand@nestjs/mercurius.Security
@nestjs/graphql@nestjs/graphqluseFactoryoruseValue@nestjs/graphql@nestjs/graphqlDateTimeandTimestampscalars accept invalid input, sonulland invalid dates reach non-null arguments@nestjs/mercuriusMercuriusFederationDriverignores subscription filters and delivers events to all subscribers@nestjs/apollo@nestjs/graphqlresolversoption defines the same type@nestjs/apollo,@nestjs/mercurius@nestjs/graphql@nestjs/graphqlresolvecallbacks run without guards when the operation is sent over HTTPBehaviour changes
Most applications need no changes. The fixes below either make silent misconfigurations fail loudly, or align runtime behaviour with what the schema and the documentation promise. Please review them before upgrading.
Startup errors for configurations that used to skip checks silently
useFactory/useValuethat uses guards, interceptors or pipes referenced by class now fails at startup; before, these enhancers never ran. Register the resolver as a class or withuseClass, or pass enhancer instances.@Plugin()classes.@ArgsType()property that collides with a named@Args();@Args()with different types or defaults.defaultValue: nullon a non-null argument or field fails at schema build. Addnullable: true, or drop the default.@ResolveField()that adds a required argument the implemented interface field doesn't declare is a schema validation error.isOneOf. Derived input types inheritisOneOf, and the@oneOfdirective now sets it.@Field(() => 'Name')) when two types share that name fails. Reference the class, or scope the types withregisterIn.MercuriusGatewayDriverwithtransformSchemafails at startup; the option used to be ignored.schemaandtypeDefs.resolverValidationOptionsnow apply to the merged schema.Requests that are now rejected
DateTime/Timestampinput is a validation error (HTTP 400). Valid date strings,Dateinstances and epoch-millisecond numbers keep working.nullresult from a custom scalar'sparseValue()/parseLiteral()is now treated as invalid input. Throw aGraphQLErrorfor input your scalar can't parse.ApolloDriver,ApolloFederationDriverandMercuriusDriver. Use WebSocket./graphql/<anything>returns 404, andpath: '/'no longer catches every URL. A trailing slash still works.'graphql-ws': falsenow disables the WebSocket endpoint. Asubscriptionsobject that enables no protocol no longer accepts upgrades.IntersectionType(). A field shared by both classes is non-null unless both allow null.validationRulesandformatError.ResolverDecoratorHost.setOnRequestStartHook()) is awaited, and if it rejects, the operation fails.Schema changes
PickType(),OmitType(),PartialType()andIntersectionType()no longer include fields inherited from a parent of another kind (e.g. an@ObjectType()parent of an@InputType()).@ResolveField()placement.include-scoped GraphQL modules.includeand@Global()modules.includeno longer pulls in resolvers of@Global()modules; list them inincludeexplicitly.@ArgsType()chains three or more levels deep is now root-first.Infinity/NaNreverse mappings and namespace-merged members are no longer enum values.protectedand#privatemembers.@HideField()also works when applied through a composed decorator.buildFederatedSchemacallbacks receive only the__resolveReferenceresolvers; the other resolvers are attached separately.Different resolvers or middleware for the same query
@ResolveField()handler, with its guards and middleware, instead of reading the property. To keep the old behaviour, declare a handler on the subtype.@Field({ middleware })and@UseFieldMiddleware()on a model field also run when the field has a@ResolveField()handler, in the order global → model → handler, each once.@InterfaceType()classes.@ResolveField(), that ends up on a type with no bound handler, returns an error and is listed in a startup warning. Before, it read the parent's property unguarded.__typenameof subclasses. The defaultresolveTypereturns the most-derived class, so__typenamenames the subclass.@Resolver()subclasses inherit the parent's type.Subscription/Mutationobject types.@ResolveField()handlers on object types namedSubscriptionorMutationare treated as field resolvers.HttpExceptioninstances are converted to GraphQL errors.#privatefields.@Extensions()are inherited by subclasses.directiveResolversis deprecated and logs a warning. It has had no effect since v9.2.0.What's Changed
e29277b)43be3d5)2307121)2d1a89c)cc19167)ed19e23)58189ba)1e678c7)c69ff53)263457c)New Contributors
Full Changelog: nestjs/graphql@v14.1.2...v14.2.0
v14.1.2Compare Source
v14.1.1Compare Source
What's Changed
Full Changelog: nestjs/graphql@v14.1.0...v14.1.1
v14.1.0Compare Source
What's Changed
New Contributors
Full Changelog: nestjs/graphql@v14.0.3...v14.1.0
v14.0.3Compare Source
v14.0.2Compare Source
v14.0.2 (2026-09-23)
Bug fixes
graphqlapollo,graphql,mercurius@apollo/subgraph'sbuildSubgraphSchema(@paemuri)Committers: 4
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.