chore(deps): update graphqlcodegenerator monorepo (major) #296
Conversation
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
renovate
bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
from
06557f2 to
2323002
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
renovate
bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
from
2323002 to
d576f4c
Compare
renovate
bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
from
d576f4c to
fd72ab2
Compare
renovate
bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
from
fd72ab2 to
ba245a2
Compare
renovate
bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
from
ba245a2 to
92d66a7
Compare
renovate
bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
from
92d66a7 to
3d1f39b
Compare
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:
^5.0.3->^6.0.0^5.0.7->^6.0.1^4.0.3->^5.0.0^4.1.6->^5.0.2^4.6.1->^5.0.2^4.5.2->^5.1.0Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/add)
v6.0.0Compare Source
Major Changes
140298aThanks @eddeee888! - Drop Node 18 supportPatch Changes
140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a]:dotansimha/graphql-code-generator (@graphql-codegen/cli)
v6.0.1Compare Source
Patch Changes
#10468
cb1b9d9Thanks @eddeee888! - In watch mode, do not write output on failurePreviously, on partial or full failure, watch mode still write to output. However, since the output'd be an empty array, it will then call
removeStaleFilesinternally to remove all previously generated files.This patch puts a temporary fix to avoid writing output on any failure to fix the described behaviour.
This also means the
config.allowPartialOutputsdoes not work in watch mode for now.v6.0.0Compare Source
Major Changes
#10218
140298aThanks @eddeee888! - Drop @graphql-tools/prisma-loader#10218
140298aThanks @eddeee888! - AddallowPartialOutputsflag to partially write successful generation to files#10218
140298aThanks @eddeee888! - Migrate inquirer to @inquirer/prompts#10218
140298aThanks @eddeee888! - Bump dependencies major versions:#10218
140298aThanks @eddeee888! - Bump listr2 to v9#10218
140298aThanks @eddeee888! - Drop Node 18 supportPatch Changes
140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a]:dotansimha/graphql-code-generator (@graphql-codegen/introspection)
v5.0.0Compare Source
Major Changes
140298aThanks @eddeee888! - Drop Node 18 supportPatch Changes
140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a]:dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v5.0.2Compare Source
Patch Changes
8258f1f]:v5.0.1Compare Source
Patch Changes
accdab6]:v5.0.0Compare Source
Major Changes
#10218
140298aThanks @eddeee888! - Remove NameNode override#10218
140298aThanks @eddeee888! - Drop Node 18 supportPatch Changes
140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)
v5.0.2Compare Source
Patch Changes
8258f1f]:v5.0.1Compare Source
Patch Changes
accdab6]:v5.0.0Compare Source
Major Changes
#10218
140298aThanks @eddeee888! - BREAKING CHANGE: Use Record<PropertyKey, never> instead of {} for empty object type#10218
140298aThanks @eddeee888! - Drop Node 18 supportPatch Changes
140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-resolvers)
v5.1.0Compare Source
Minor Changes
8258f1fThanks @eddeee888! - AddaddInterfaceFieldResolverTypesoption to support custom Interface resolver inheritance behaviour (such as the one enabled by makeExecutableSchema's inheritResolversFromInterfaces)Patch Changes
8258f1f]:v5.0.1Compare Source
Patch Changes
accdab6]:v5.0.0Compare Source
Major Changes
#10218
140298aThanks @eddeee888! - BREAKING CHANGES: Do not generate __isTypeOf for non-implementing types or non-union members#10218
140298aThanks @eddeee888! - BREAKING CHANGE: Use Record<PropertyKey, never> instead of {} for empty object type#10218
140298aThanks @eddeee888! - Ensure Federation Interfaces have__resolveReferenceif they are resolvable entitiesBREAKING CHANGES: Deprecate
onlyResolveTypeForInterfacesbecause majority of use cases cannot implement resolvers in Interfaces. Interface normal resolvers are not generated by default. UseaddInterfaceFieldResolverTypesoption released in@graphql-codegen/typescript-resolvers@5.1.0to support custom Interface resolver inheritance behaviour (such as the one enabled by makeExecutableSchema's inheritResolversFromInterfaces)BREAKING CHANGES: Deprecate
generateInternalResolversIfNeeded.__resolveReferencebecause types do not have__resolveReferenceif they are not Federation entities or are not resolvable. Users should not have to manually set this option. This option was put in to wait for this major version.#10218
140298aThanks @eddeee888! - BREAKING CHANGE: Improve Federation Entity's resolvers' parent param type: These types were using reference types inline. This makes it hard to handle mappers. The Parent type now all comes from ParentResolverTypes to make handling mappers and parent types simpler.#10218
140298aThanks @eddeee888! - Fixmappersusage with Federationmapperswas previously used as__resolveReference's first param (usually called "reference"). However, this is incorrect becausereferenceinterface comes directly from@keyand@requiresdirectives. This patch fixes the issue by creating a newFederationTypestype and use it as the base for federation entity types when being used to type entity references.BREAKING CHANGES: No longer generate
UnwrappedObjectutility type, as this was used to support the wrong previously generated type.#10218
140298aThanks @eddeee888! - Drop Node 18 supportMinor Changes
140298aThanks @eddeee888! - Report to meta user defined objects whether they have isTypeOf resolverPatch Changes
#10218
140298aThanks @eddeee888! - Update @requires type#10218
140298aThanks @eddeee888! - Fix fields or object types marked with @external being wrongly generatedUpdated dependencies [
140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.