Skip to content

Update graphqlcodegenerator monorepo (major) - #49

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

Update graphqlcodegenerator monorepo (major)#49
renovate-s-holblin[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphqlcodegenerator-monorepo

Conversation

@renovate-s-holblin

@renovate-s-holblin renovate-s-holblin Bot commented May 4, 2026 •
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 Confidence
@graphql-codegen/cli (source) 6.2.1 → 7.0.0 age confidence
@graphql-codegen/client-preset (source) 5.2.4 → 6.0.0 age confidence
@graphql-codegen/typescript (source) ^5.0.9 → ^6.0.1 age confidence
@graphql-codegen/typescript-resolvers (source) ^5.1.7 → ^6.0.1 age confidence

Release Notes

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

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
dotansimha/graphql-code-generator (@​graphql-codegen/client-preset)

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! - 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: 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! - BREAKING CHANGES: The default hashing
    algorithm is now sha256 instead of sha1. Generated sha256 format also follows the standard
    outlined in
    https://github.com/graphql/graphql-over-http/blob/52d56fb36d51c17e08a920510a23bdc2f6a720be/spec/Appendix%20A%20--%20Persisted%20Documents.md#sha256-hex-document-identifier

  • #​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

Patch Changes

v5.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
dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v6.0.1

Compare Source

Patch Changes

v6.0.0

Compare Source

Major Changes

  • #​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: 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: 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: Remove unused utility types
    from typescript plugin as they were previously used for typescript-operations plugin:

    • MakeOptional
    • MakeMaybe
    • MakeEmpty
    • Incremental

    BREAKING CHANGE: Remove getRootTypeNames function because it's available in
    @graphql-utils/tools and not used anywhere

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

v5.0.10

Compare Source

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

v6.0.1

Compare Source

Patch Changes

v6.0.0

Compare Source

Major Changes

  • #​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: 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

Patch Changes

v5.1.8

Compare Source

Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • 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.

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

This PR has been generated by Mend Renovate.

@renovate-s-holblin
renovate-s-holblin Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from ad1a5d0 to 5b91ea7 Compare May 6, 2026 15:06
@renovate-s-holblin
renovate-s-holblin Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 5b91ea7 to 53bfe01 Compare May 10, 2026 06:34
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 major

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants