Repository navigation
chore(deps): update graphqlcodegenerator monorepo (major) - #438
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
3 times, most recently
from
November 15, 2026 10:01
05fdc8e to
ae971e4
Compare
renovate
Bot
force-pushed
the
renovate/major-graphqlcodegenerator-monorepo
branch
from
November 15, 2026 14:02
ae971e4 to
351332e
Compare
This branch has not been deployed
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:
7.4.6→8.0.06.1.1→7.0.06.1.2→7.0.16.1.1→7.0.07.1.0→8.0.26.2.0→7.0.1Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v8.0.0Compare Source
Major Changes
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
longer supported. The
graphqlpeer dependency is now^16.0.0 || ^17.0.0, so upgradegraphqlto version 16 or 17 before updating to this version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Node.js versions below
22.18.0 are no longer supported. Upgrade to Node.js 22.18.0 or later before updating to this
version.
#11075
fa49a37Thanks @eddeee888! -
generate()now returnsPromise<FileOutput[] | void>instead ofPromise<FileOutput[] | any>. The result is no longerany, so consumers using the result as an array must narrow it first.Refs #11071
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Remove the deprecated
emitLegacyCommonJSImportsconfig option and the--emit-legacy-common-js-importsCLI flagUse
importExtension(or--import-extension) to set the extension appended to relative imports.When
importExtensionis not set, no extension is appended.@graphql-codegen/plugin-helpersno longer exportsnormalizeImportExtension. UseimportExtension ?? ''instead.Migration:
const config: CodegenConfig = { - emitLegacyCommonJSImports: false, + importExtension: '.js', };#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE:
@graphql-tools/*dependencies are updated to their latest majors, which require Node.js 22.18.0 or later and
GraphQL 16 or 17. If you import
@graphql-tools/*packages in your own code, update them to thesame majors to avoid duplicate installs.
@graphql-tools/code-file-loader@9now extracts#graphql-marked template literals by default, so code files that contain such templates canproduce newly found documents; check your generated output after upgrading. To keep the previous
behavior, set
pluckConfig: { gqlHashComment: '' }.#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE -
config.generatesnolonger takes
ConfiguredPlugin[], takesConfiguredOutput[]insteadconfig.generates's previous typing allowed a value to be an array e.g.However, this never worked because this config is eventually passed into
normalizeOutputParamwhich previously had this bug in the implementation:
Now, an array is still accepted, but as
ConfiguredOutput[]instead. For this major versionrelease, only the first array element is used, and
@graphql-codegen/clilogs a warning whenthere is more than one element.
normalizeOutputParamnow returnsConfiguredOutput[]instead of a singleConfiguredOutput.@graphql-codegen/clialso throws its "Invalid Codegen Configuration" error when ageneratesarray is empty or its first element is not a config object. This error is now a single generic
message, no longer naming the output file, and it shows a TypeScript
CodegenConfigexample withthe
ConfiguredOutputshape instead of the old YAML plugin-list example.Patch Changes
#11075
fa49a37Thanks @eddeee888! - dependencies updates:
@graphql-tools/apollo-engine-loader@^9.0.2↗︎(from
^8.0.38, independencies)@graphql-tools/code-file-loader@^9.0.3↗︎(from
^8.1.41, independencies)@graphql-tools/git-loader@^9.0.3↗︎(from
^8.0.44, independencies)@graphql-tools/github-loader@^10.0.3↗︎(from
^9.1.11, independencies)@graphql-tools/graphql-file-loader@^9.0.2↗︎(from
^8.1.22, independencies)@graphql-tools/json-file-loader@^9.0.2↗︎(from
^8.0.36, independencies)@graphql-tools/load@^9.0.2↗︎(from
^8.1.19, independencies)@graphql-tools/merge@^10.0.2↗︎(from
^9.2.6, independencies)@graphql-tools/url-loader@^10.0.2↗︎(from
^9.1.12, independencies)@graphql-tools/utils@^13.0.2↗︎(from
^12.0.3, independencies)graphql-config@^6.0.0↗︎ (from^5.1.8, independencies)graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)#11075
fa49a37Thanks @eddeee888! - dependencies updates:
@graphql-tools/apollo-engine-loader@^9.0.2↗︎(from
^8.0.38, independencies)@graphql-tools/code-file-loader@^9.0.3↗︎(from
^8.1.41, independencies)@graphql-tools/git-loader@^9.0.3↗︎(from
^8.0.44, independencies)@graphql-tools/github-loader@^10.0.3↗︎(from
^9.1.11, independencies)@graphql-tools/graphql-file-loader@^9.0.2↗︎(from
^8.1.22, independencies)@graphql-tools/json-file-loader@^9.0.2↗︎(from
^8.0.36, independencies)@graphql-tools/load@^9.0.2↗︎(from
^8.1.19, independencies)@graphql-tools/merge@^10.0.2↗︎(from
^9.2.6, independencies)@graphql-tools/url-loader@^10.0.2↗︎(from
^9.1.12, independencies)@graphql-tools/utils@^13.0.2↗︎(from
^12.0.3, independencies)graphql-config@^6.0.0↗︎ (from^5.1.8, independencies)graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)#11075
fa49a37Thanks @eddeee888! - dependencies updates:
graphql-config@^6.0.0↗︎ (from^5.1.8, independencies)Updated dependencies
[
fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,409ffbf,fa49a37,fa49a37,7366c63,fa49a37,fa49a37]:dotansimha/graphql-code-generator (@graphql-codegen/schema-ast)
v7.0.0Compare Source
Major Changes
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
longer supported. The
graphqlpeer dependency is now^16.0.0 || ^17.0.0, so upgradegraphqlto version 16 or 17 before updating to this version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Node.js versions below
22.18.0 are no longer supported. Upgrade to Node.js 22.18.0 or later before updating to this
version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: A plugin's
validatefunction now receives an info object as its fourth argument, matching the
pluginfunction:validate(schema, documents, config, { outputFile, allPlugins, pluginContext }). Custom pluginsthat export
validateand readoutputFile,allPluginsorpluginContextas positionalarguments must destructure them from the fourth argument instead.
Refs #11071
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Remove the
commentDescriptionsoption fromSchemaASTConfig. It has had no effect since graphql 16, whichno longer prints descriptions as comments. Delete it from your
schema-astconfig; the generatedoutput does not change.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE:
@graphql-tools/*dependencies are updated to their latest majors, which require Node.js 22.18.0 or later and
GraphQL 16 or 17. If you import
@graphql-tools/*packages in your own code, update them to thesame majors to avoid duplicate installs.
@graphql-tools/code-file-loader@9now extracts#graphql-marked template literals by default, so code files that contain such templates canproduce newly found documents; check your generated output after upgrading. To keep the previous
behavior, set
pluckConfig: { gqlHashComment: '' }.Patch Changes
#11075
fa49a37Thanks @eddeee888! - dependencies updates:
@graphql-tools/utils@^13.0.2↗︎(from
^12.0.3, independencies)graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)#11075
fa49a37Thanks @eddeee888! - dependencies updates:
@graphql-tools/utils@^12.0.3↗︎(from
dependencies)graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)#11075
fa49a37Thanks @eddeee888! - Remove unused
@graphql-tools/utilsdependency
Updated dependencies
[
fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37]:dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v7.0.1Compare Source
Patch Changes
#11099
6138e3fThanks @ewerton336! - Fix
typesPrefixbeing applied to enumkeys when generating enums as
const(enumsAsConst: trueorenumType: 'const')Updated dependencies
[
6138e3f]:v7.0.0Compare Source
Major Changes
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
longer supported. The
graphqlpeer dependency is now^16.0.0 || ^17.0.0, so upgradegraphqlto version 16 or 17 before updating to this version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Node.js versions below
22.18.0 are no longer supported. Upgrade to Node.js 22.18.0 or later before updating to this
version.
Patch Changes
#11075
fa49a37Thanks @eddeee888! - dependencies updates:
graphql@^16.0.0 || ^17.0.0↗︎ (from^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0, inpeerDependencies)#11075
fa49a37Thanks @eddeee888! - dependencies updates:
graphql@^16.0.0 || ^17.0.0↗︎ (from^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0, inpeerDependencies)Updated dependencies
[
fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,409ffbf,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-document-nodes)
v7.0.0Compare Source
Major Changes
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
longer supported. The
graphqlpeer dependency is now^16.0.0 || ^17.0.0, so upgradegraphqlto version 16 or 17 before updating to this version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Node.js versions below
22.18.0 are no longer supported. Upgrade to Node.js 22.18.0 or later before updating to this
version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: A plugin's
validatefunction now receives an info object as its fourth argument, matching the
pluginfunction:validate(schema, documents, config, { outputFile, allPlugins, pluginContext }). Custom pluginsthat export
validateand readoutputFile,allPluginsorpluginContextas positionalarguments must destructure them from the fourth argument instead.
Refs #11071
Patch Changes
#11075
fa49a37Thanks @eddeee888! - dependencies updates:
graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)#11075
fa49a37Thanks @eddeee888! - dependencies updates:
graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)Updated dependencies
[
fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,409ffbf,fa49a37,fa49a37,fa49a37,fa49a37]:dotansimha/graphql-code-generator-community (@graphql-codegen/typescript-graphql-request)
v8.0.2Compare Source
Patch Changes
ed49d00Thanks @eddeee888! - This changes the shape of generated
documents: a fragment's
*Docno longer interpolates the fragments it spreads, and each operationdocument instead interpolates every fragment it transitively spreads. Generated output is
equivalent, but any code or snapshot asserting on the previous interpolation layout needs
updating. Also,
documentMode: 'string'is now remapped to'plainString'with a consolewarning, because the
'string'output referenced an undeclaredTypedDocumentString. Documentsare now typed as plain
string; if you suppliedTypedDocumentStringyourself (e.g. via theaddplugin) or relied on theTypedDocumentString<Result, Variables>type of exporteddocuments, please check your setup. Set
documentMode: 'plainString'to silence the warning.v8.0.1Compare Source
Patch Changes
#1720
86dd614Thanks @eddeee888! - Bump
@graphql-tools/utilsand@graphql-tools/schemato the latest majors.@graphql-codegen/flow-resolvers:engines.nodeis now>=22.18.0, as required by the new@graphql-tools/utilsmajor.@graphql-codegen/typescript-jit-sdk: the@graphql-tools/utilspeer range is now^13.0.0.v8.0.0Compare Source
Major Changes
#1711
fb443c1Thanks @eddeee888! - Move to graphql-codegen v8.
@graphql-codegen/plugin-helpersand@graphql-codegen/visitor-plugin-commonto^8.0.0graphqlpeer dependency to^16.0.0 || ^17.0.0>=22.18.0validatereadsoutputFilefrom the v8infoargumentPatch Changes
fb443c1Thanks @eddeee888! - dependencies updates:
@graphql-codegen/plugin-helpers@^8.0.0↗︎(from
^6.3.0, independencies)@graphql-codegen/visitor-plugin-common@^8.0.0↗︎(from
^6.3.0, independencies)graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0,in
peerDependencies)dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)
v7.0.1Compare Source
Patch Changes
#11099
6138e3fThanks @ewerton336! - Fix
typesPrefixbeing applied to enumkeys when generating enums as
const(enumsAsConst: trueorenumType: 'const')Updated dependencies
[
6138e3f]:v7.0.0Compare Source
Major Changes
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
longer supported. The
graphqlpeer dependency is now^16.0.0 || ^17.0.0, so upgradegraphqlto version 16 or 17 before updating to this version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Node.js versions below
22.18.0 are no longer supported. Upgrade to Node.js 22.18.0 or later before updating to this
version.
#11075
fa49a37Thanks @eddeee888! - BREAKING CHANGE: Remove the deprecated
emitLegacyCommonJSImportsconfig option and the--emit-legacy-common-js-importsCLI flagUse
importExtension(or--import-extension) to set the extension appended to relative imports.When
importExtensionis not set, no extension is appended.@graphql-codegen/plugin-helpersno longer exportsnormalizeImportExtension. UseimportExtension ?? ''instead.Migration:
const config: CodegenConfig = { - emitLegacyCommonJSImports: false, + importExtension: '.js', };Minor Changes
#11103
409ffbfThanks @jerelmiller! - Add support for graphql v17 fragment
arguments (
experimentalFragmentArguments).To use fragment arguments, set the parser option in the root
config:Patch Changes
#11075
fa49a37Thanks @eddeee888! - dependencies updates:
graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)#11075
fa49a37Thanks @eddeee888! - dependencies updates:
graphql@^16.0.0 || ^17.0.0↗︎ (from^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0,in
peerDependencies)Updated dependencies
[
fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,409ffbf,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37,fa49a37]:Configuration
📅 Schedule: (UTC)
🚦 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.