Skip to content

chore(deps): update graphqlcodegenerator monorepo (major) - #438

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-graphqlcodegenerator-monorepo
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-graphqlcodegenerator-monorepo

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/cli (source) 7.4.6 → 8.0.0 age confidence
@graphql-codegen/schema-ast (source) 6.1.1 → 7.0.0 age confidence
@graphql-codegen/typescript (source) 6.1.2 → 7.0.1 age confidence
@graphql-codegen/typescript-document-nodes (source) 6.1.1 → 7.0.0 age confidence
@graphql-codegen/typescript-graphql-request (source) 7.1.0 → 8.0.2 age confidence
@graphql-codegen/typescript-operations (source) 6.2.0 → 7.0.1 age confidence

Release Notes

dotansimha/graphql-code-generator (@​graphql-codegen/cli)

v8.0.0

Compare Source

Major Changes
  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
    longer supported. The graphql peer dependency is now ^16.0.0 || ^17.0.0, so upgrade graphql
    to version 16 or 17 before updating to this version.

  • #​11075
    fa49a37
    Thanks @​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
    fa49a37
    Thanks @​eddeee888! - generate() now returns
    Promise<FileOutput[] | void> instead of Promise<FileOutput[] | any>. The result is no longer
    any, so consumers using the result as an array must narrow it first.

    Refs #​11071

  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: Remove the deprecated
    emitLegacyCommonJSImports config option and the --emit-legacy-common-js-imports CLI flag

    Use importExtension (or --import-extension) to set the extension appended to relative imports.
    When importExtension is not set, no extension is appended.

    @graphql-codegen/plugin-helpers no longer exports normalizeImportExtension. Use
    importExtension ?? '' instead.

    Migration:

     const config: CodegenConfig = {
    -  emitLegacyCommonJSImports: false,
    +  importExtension: '.js',
     };
  • #​11075
    fa49a37
    Thanks @​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 the
    same majors to avoid duplicate installs. @graphql-tools/code-file-loader@9 now extracts
    #graphql-marked template literals by default, so code files that contain such templates can
    produce newly found documents; check your generated output after upgrading. To keep the previous
    behavior, set pluckConfig: { gqlHashComment: '' }.

  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE - config.generates no
    longer takes ConfiguredPlugin[], takes ConfiguredOutput[] instead

    config.generates's previous typing allowed a value to be an array e.g.

    generates: {
      "src/gql/generated.ts": [{ typescript: {} }]
    }
    

    However, this never worked because this config is eventually passed into normalizeOutputParam
    which previously had this bug in the implementation:

    export function normalizeOutputParam(config) {
      // 0. When config is an array...
      if (isOutputConfigArray(config)) {
        // 1. `isOutputConfigArray(config)` was `Array.isArray(config)` -> returns true
        return {
          documents: [],
          schema: [],
          plugins: isConfiguredOutput(config) ? config.plugins : config // 2. ‼️ `isConfiguredOutput(config)` was `typeof config === 'object'` -> returns true. This is a bug because we are accessing `plugins` property of an array, which will ALWAYS be `undefined` -> the output is always rejected as "Invalid Codegen Configuration"
        }
      }
      if (isConfiguredOutput(config)) {
        return config
      }
      throw new Error(`Invalid "generates" config!`)
    }

    Now, an array is still accepted, but as ConfiguredOutput[] instead. For this major version
    release, only the first array element is used, and @graphql-codegen/cli logs a warning when
    there is more than one element.

    normalizeOutputParam now returns ConfiguredOutput[] instead of a single ConfiguredOutput.

    @graphql-codegen/cli also throws its "Invalid Codegen Configuration" error when a generates
    array 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 CodegenConfig example with
    the ConfiguredOutput shape instead of the old YAML plugin-list example.

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/schema-ast)

v7.0.0

Compare Source

Major Changes
  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
    longer supported. The graphql peer dependency is now ^16.0.0 || ^17.0.0, so upgrade graphql
    to version 16 or 17 before updating to this version.

  • #​11075
    fa49a37
    Thanks @​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
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: A plugin's validate
    function now receives an info object as its fourth argument, matching the plugin function:
    validate(schema, documents, config, { outputFile, allPlugins, pluginContext }). Custom plugins
    that export validate and read outputFile, allPlugins or pluginContext as positional
    arguments must destructure them from the fourth argument instead.

    Refs #​11071

  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: Remove the
    commentDescriptions option from SchemaASTConfig. It has had no effect since graphql 16, which
    no longer prints descriptions as comments. Delete it from your schema-ast config; the generated
    output does not change.

  • #​11075
    fa49a37
    Thanks @​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 the
    same majors to avoid duplicate installs. @graphql-tools/code-file-loader@9 now extracts
    #graphql-marked template literals by default, so code files that contain such templates can
    produce newly found documents; check your generated output after upgrading. To keep the previous
    behavior, set pluckConfig: { gqlHashComment: '' }.

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes
  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
    longer supported. The graphql peer dependency is now ^16.0.0 || ^17.0.0, so upgrade graphql
    to version 16 or 17 before updating to this version.

  • #​11075
    fa49a37
    Thanks @​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
dotansimha/graphql-code-generator (@​graphql-codegen/typescript-document-nodes)

v7.0.0

Compare Source

Major Changes
  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
    longer supported. The graphql peer dependency is now ^16.0.0 || ^17.0.0, so upgrade graphql
    to version 16 or 17 before updating to this version.

  • #​11075
    fa49a37
    Thanks @​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
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: A plugin's validate
    function now receives an info object as its fourth argument, matching the plugin function:
    validate(schema, documents, config, { outputFile, allPlugins, pluginContext }). Custom plugins
    that export validate and read outputFile, allPlugins or pluginContext as positional
    arguments must destructure them from the fourth argument instead.

    Refs #​11071

Patch Changes
dotansimha/graphql-code-generator-community (@​graphql-codegen/typescript-graphql-request)

v8.0.2

Compare Source

Patch Changes
  • #​1657
    ed49d00
    Thanks @​eddeee888! - This changes the shape of generated
    documents: a fragment's *Doc no longer interpolates the fragments it spreads, and each operation
    document 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 console
    warning, because the 'string' output referenced an undeclared TypedDocumentString. Documents
    are now typed as plain string; if you supplied TypedDocumentString yourself (e.g. via the
    add plugin) or relied on the TypedDocumentString<Result, Variables> type of exported
    documents, please check your setup. Set documentMode: 'plainString' to silence the warning.

v8.0.1

Compare Source

Patch Changes
  • #​1720
    86dd614
    Thanks @​eddeee888! - Bump @graphql-tools/utils and
    @graphql-tools/schema to the latest majors.

    • @graphql-codegen/flow-resolvers: engines.node is now >=22.18.0, as required by the new
      @graphql-tools/utils major.
    • @graphql-codegen/typescript-jit-sdk: the @graphql-tools/utils peer range is now ^13.0.0.

v8.0.0

Compare Source

Major Changes
  • #​1711
    fb443c1
    Thanks @​eddeee888! - Move to graphql-codegen v8.

    • Bump @graphql-codegen/plugin-helpers and @graphql-codegen/visitor-plugin-common to ^8.0.0
    • Narrow the graphql peer dependency to ^16.0.0 || ^17.0.0
    • Require Node.js >=22.18.0
    • validate reads outputFile from the v8 info argument
Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typescript-operations)

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes
  • #​11075
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: GraphQL 14 and 15 are no
    longer supported. The graphql peer dependency is now ^16.0.0 || ^17.0.0, so upgrade graphql
    to version 16 or 17 before updating to this version.

  • #​11075
    fa49a37
    Thanks @​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
    fa49a37
    Thanks @​eddeee888! - BREAKING CHANGE: Remove the deprecated
    emitLegacyCommonJSImports config option and the --emit-legacy-common-js-imports CLI flag

    Use importExtension (or --import-extension) to set the extension appended to relative imports.
    When importExtension is not set, no extension is appended.

    @graphql-codegen/plugin-helpers no longer exports normalizeImportExtension. Use
    importExtension ?? '' instead.

    Migration:

     const config: CodegenConfig = {
    -  emitLegacyCommonJSImports: false,
    +  importExtension: '.js',
     };
Minor Changes
  • #​11103
    409ffbf
    Thanks @​jerelmiller! - Add support for graphql v17 fragment
    arguments (experimentalFragmentArguments).

    To use fragment arguments, set the parser option in the root config:

    const config: CodegenConfig = {
      config: { experimentalFragmentArguments: true }
      // ...
    }
Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "after 6am and before 10am on saturday"
  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the renovate label Nov 14, 2026
@mystique-as-code mystique-as-code Bot added maintenance Maintenance work. ui labels Nov 14, 2026
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 05fdc8e to ae971e4 Compare November 15, 2026 10:01
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from ae971e4 to 351332e Compare November 15, 2026 14:02

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants