Skip to content

chore(deps): update graphqlcodegenerator monorepo (major)#8144

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

chore(deps): update graphqlcodegenerator monorepo (major)#8144
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphqlcodegenerator-monorepo

Conversation

@renovate

@renovate renovate Bot commented Sep 8, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-codegen/cli (source) 5.0.7 → 7.2.0 age adoption passing confidence
@graphql-codegen/typescript-operations (source) 4.6.1 → 6.1.0 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

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

v7.2.0

Compare Source

Minor Changes
Patch Changes

v7.1.3

Compare Source

Patch Changes

  • #​10335
    3280ace
    Thanks @​Diluka! - Fix graphql-config loading order to correctly
    detect codegen projects

    Previously, a graphql-config file like this failed:

    projects:
  default:
    schema: 'default/schema.graphql'
  project1:
    schema: 'project1/schema.graphql'
    extensions:
      codegen:
        generates:
          'project1/__generated__/types.ts':
            plugins: ['typescript']

    This is because the default project doesn't have a codegen extension, which caused previous
    logic to short circuit before reading project1's config.

    The fix reads every named project first, before reading the default project to exhaustively go
    through every single project.

v7.1.2

Compare Source

Patch Changes

v7.1.1

Compare Source

Patch Changes

v7.1.0

Compare Source

Minor Changes
Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Update deps to latest, some
    only support ESM

    Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
    means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
    ESM-only packages.

    If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
    issues when running Jest tests, try using Vitest.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Drop Node 20 support

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Set noSilentErrors: true
    by default

    When multiple files match documents pattern, and there are syntax errors in some but not others,
    then the operations with errors are not included in the loaded documents list by default
    (noSilentErrors: false). This is annoying for users as there is no feedback loop during
    development.

    noSilentErrors: true is used as the default for Codegen users to make the feedback loop faster.
    It can still overriden in Codegen Config if desired.

Patch Changes

v6.3.1

Compare Source

Patch Changes
  • #​10737
    be85118
    Thanks @​eddeee888! - Fix issue where same SDL in different
    documents are ignored when handling documents vs externalDocuments

v6.3.0

Compare Source

Minor Changes

  • #​10659
    e65d303
    Thanks @​ikusakov2! - Add support for externalDocuments

    externalDocuments declares GraphQL documents that will be read but will not have type files
    generated for them. These documents are available to plugins for type resolution (e.g. fragment
    types), but no output files will be generated based on them. Accepts the same formats as
    documents.

    This config option is useful for monorepos where each project may want to generate types for its
    own documents, but some may need to read shared fragments from across projects.

Patch Changes

v6.2.1

Compare Source

Patch Changes
  • #​10618
    e804925
    Thanks @​PalmerTurley34! - Honor per-output preset
    importExtension and emitLegacyCommonJSImports config instead of always using the root config
    values.

v6.2.0

Compare Source

Minor Changes
Patch Changes

v6.1.3

Compare Source

Patch Changes

v6.1.2

Compare Source

Patch Changes
  • #​10590
    e173e11
    Thanks @​ya2s! - Fix GraphQL Config loading to forward nested
    extensions.codegen.config options when loading schemas/documents, matching codegen.ts
    behavior.

v6.1.1

Compare Source

Patch Changes

  • #​10569
    8cb7d43
    Thanks @​etr2460! - fix(graphql-codegen-cli): Don't hang when 0 CPUs
    are found

    Fixes generation when 0 CPUs are returned by os.cpus(), which occurs in sandbox environments.

v6.1.0

Compare Source

Minor Changes
Patch Changes

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes

  • #​10468
    cb1b9d9
    Thanks @​eddeee888! - In watch mode, do not write output on failure

    Previously, on partial or full failure, watch mode still write to output. However, since the
    output'd be an empty array, it will then call removeStaleFiles internally 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.allowPartialOutputs does not work in watch mode for now.

v6.0.0

Compare Source

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

v6.1.0

Compare Source

Minor Changes
Patch Changes

v6.0.5

Compare Source

Patch Changes

v6.0.4

Compare Source

Patch Changes

v6.0.3

Compare Source

Patch Changes

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes

v6.0.0

Compare Source

Major Changes

  • #​10496
    afaace6
    Thanks @​eddeee888! - Fix nullable field optionality in operations

    Previously, a nullable Result field is generated as optional (marked by ? TypeScript modifier)
    by default. This is not correct, because generally at runtime such field can only be null, and
    not undefined (both missing from the object OR undefined). The only exceptions are when fields
    are deferred (using @defer directive) or marked as conditional (using @skip or @include).

    Now, a nullable Result field cannot be optional unless the exceptions are met. This also limits
    avoidOptionals to only target Variables input, since some users may want to force explicit
    null when providing operation variables.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: visitors' config option are
    moved based on their use case

    • addTypename/skipTypename: is only a types-visitor concern. This is moved to types-visitor from
      base-visitor
    • nonOptionalTypename: is a documents-visitor and types-visitor concern. Moved from base-visitor
      there
    • extractAllFieldsToTypes: is a documents-visitor concern. Moved from base-visitor there
    • enumPrefix and enumSuffix: need to be in base-visitor as all 3 types of visitors need this to
      correctly sync the enum type names. This is moved to base visitor
    • ignoreEnumValuesFromSchema: is a documents-visitor and types-visitor concern. Moved from
      base-visitor there.
    • globalNamespace: is a documents-visitor concern. Moved from base-visitor there

    Refactors

    • documents-visitor no longer extends types-visitor option types as they have two distinct
      usages now. The types now extend base-visitor types. This is now consistent with
      documents-visitor extending base-visitor
    • Classes now handle config parsing and types at the same level e.g. if typescript-operations
      plugin parses configOne, then the types for configOne must be in that class, rather than in
      base-documents-visitor

    Note: These visitors are rolled up into one type for simplicity

    • base-visitor: includes base-visitor
    • documents-visitor: includes base-documents-visitor and typescript-operations visitor
    • types-visitor: includes base-types-visitor and typescript visitor
    • resolvers-visitor: includes base-resolvers-visitor and typescript-resolvers visitor

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: typescript-operations plugin
    now generates enum if it is used in operation.

  • #​10496
    afaace6
    Thanks @​eddeee888! - Conditionally generate input types and output
    enums into target file

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: make unknown instead of
    any the default custom scalar type

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Update deps to latest, some
    only support ESM

    Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
    means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
    ESM-only packages.

    If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
    issues when running Jest tests, try using Vitest.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Drop Node 20 support

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Decouple
    typescript-operations plugin from typescript plugin

    Previously, TypeScriptOperationVariablesToObject from typescript-operations was extending from
    typescript plugin. This made it (1) very hard to read, as we need to jump from base class <->
    typescript class <-> typescript-operations class to understand the flow and (2) very hard to
    evolve the two independently (which is the point of this work).

    Since there's not much shared logic anyways, it's simpler to extend the typescript-operations
    class from the base class directly.

  • #​10496
    afaace6
    Thanks @​eddeee888! - The typescript-operations plugin no longer
    generates InputMaybe and Scalars types; it now uses native Typescript types instead.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: typescript plugin no
    longer generates Exact utility type. Instead, typescript-operations generates said utility
    type for every file it creates. This is because it is used only for Variables, so we only need
    to generate it once for every generated operation file.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Operation plugin and Client
    Preset no longer generates optional __typename for result type

    __typenam should not be in the request unless:

    • explicitly requested by the user
    • automatically injected into the request by clients, such as Apollo Clients.

    Note: Apollo Client users can still use nonOptionalTypename: true and
    skipTypeNameForRoot: true to ensure generated types match the runtime behaviour.

  • #​10496
    afaace6
    Thanks @​eddeee888! - Integrate new typescript-operations into
    client-preset

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: config.avoidOptionals now
    only supports object, inputValue, defaultValue

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: rename avoidOptionals.object
    to avoidOptionals.variableValue

Minor Changes

  • #​10496
    afaace6
    Thanks @​eddeee888! - Add support for declarationKind for
    typescript-operations

    • Input: can only be type or interface
    • Variables: no support. It must always be type because it's an alias e.g.
      Variables = Exact<{ something: type }>
    • Result: can only be type or interface
      • Note: when extractAllFieldsToTypes:true or extractAllFieldsToTypesCompact:true, Results
        are used as type alias, so they are forced to be type. There is a console warning for users.

  • #​10496
    afaace6
    Thanks @​eddeee888! - Add importSchemaTypesFrom support

  • #​10496
    afaace6
    Thanks @​eddeee888! - Add generateOperationTypes to
    typescript-operations to allow omitting operation types such as Variables,
    Query/Mutation/Subscription selection set, and Fragment types

  • #​10496
    afaace6
    Thanks @​eddeee888! - Fixing 2 bugs: 1) including enums from
    external fragments; 2) extractAllFieldsToTypesCompact does not create duplicates

Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 🎄 dependencies Updates to dependencies, generally automatically managed by Renovate. label Sep 8, 2025
@apollo-librarian

apollo-librarian Bot commented Sep 8, 2025 •
edited
Loading

Copy link
Copy Markdown

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: b0bd5583a5ce0f5ab4f5dbcc
Build Logs: View logs

✅ AI Style Review — No Changes Detected

No MDX files were changed in this pull request.

Review Log: View detailed log

This review is AI-generated. Please use common sense when accepting these suggestions, as they may not always be accurate or appropriate for your specific context.

@codesandbox-ci

codesandbox-ci Bot commented Sep 8, 2025 •
edited
Loading

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 491f84f to 09a2bca Compare September 27, 2025 09:32
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 9c75466 to c83b745 Compare October 5, 2025 17:28
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 63ec01a to 93a6247 Compare October 25, 2025 08:53
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 93a6247 to ed1fd21 Compare November 1, 2025 10:47
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from cb2d73b to 6601b41 Compare November 22, 2025 09:16
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 8e8d1a4 to 1c9beab Compare December 6, 2025 09:24
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1c9beab to fce9d72 Compare December 20, 2025 09:40
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from abbf86d to befceaf Compare January 11, 2026 12:46
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from befceaf to eea4805 Compare January 24, 2026 09:12
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from eea4805 to 70665a0 Compare February 7, 2026 09:40
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from b49313d to d2e3807 Compare February 21, 2026 09:07
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d2e3807 to 32effc9 Compare February 22, 2026 17:39
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 32effc9 to 18e33ab Compare March 7, 2026 10:40
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 18e33ab to c883705 Compare March 14, 2026 16:05
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from c883705 to 1b6a947 Compare March 28, 2026 09:42
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0f12121 to 7fc55d3 Compare April 11, 2026 08:42
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 3d2a1bb to 5663351 Compare April 18, 2026 13:48
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from ba5a2d7 to 640be81 Compare May 2, 2026 08:37
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from ad346a4 to 293af3e Compare May 16, 2026 09:16
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 293af3e to e3eb477 Compare May 23, 2026 09:38
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 20b0456 to 226c813 Compare June 6, 2026 08:54
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 226c813 to 04d7f6a Compare June 13, 2026 08:51
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from df03600 to a039717 Compare June 27, 2026 08:51
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a039717 to b95346f Compare July 11, 2026 11:35
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from b95346f to 8cafa8a Compare July 12, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

🎄 dependencies Updates to dependencies, generally automatically managed by Renovate.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@muntianus