Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Mar 22, 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.0.0 → ^7.0.0 age confidence
@graphql-codegen/typescript (source) ^5.0.0 → ^6.0.0 age confidence
@graphql-codegen/typescript-operations (source) ^5.0.0 → ^6.0.0 age confidence
@graphql-codegen/typescript-vue-apollo (source) ^4.1.1 → ^5.0.0 age confidence

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

v6.1.0

Compare Source

Minor Changes
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! - 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

v5.0.9

Compare Source

Patch Changes

v5.0.8

Compare Source

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

v6.1.2

Compare Source

Patch Changes

v6.1.1

Compare Source

Patch Changes

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 `und

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • "on monday"
  • 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 requested a review from corrupt952 March 22, 2026 17:41
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch from a9332ce to 437e7e2 Compare April 8, 2026 18:58
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch from 437e7e2 to 5f47c61 Compare April 22, 2026 13:59
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch from 5f47c61 to 5809deb Compare May 4, 2026 00:17
@renovate renovate Bot changed the title chore(deps): update dependency @graphql-codegen/typescript-vue-apollo to v5 chore(deps): update graphqlcodegenerator monorepo (major) May 4, 2026
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch 2 times, most recently from dc2ef2d to 8395c8e Compare May 12, 2026 10:13
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch from 8395c8e to 9e754c4 Compare May 18, 2026 15:59
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch 6 times, most recently from c2a5ba5 to e91eb5b Compare June 4, 2026 11:51
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch from e91eb5b to 48da927 Compare June 11, 2026 14:56
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch 2 times, most recently from ce0c1e1 to 38602be Compare June 19, 2026 15:55
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch from 38602be to 2b19fa8 Compare June 27, 2026 14:41
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0300f52 to 32285aa Compare July 12, 2026 10:58
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch 3 times, most recently from bdb1edd to 677d344 Compare July 23, 2026 15:01
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch 2 times, most recently from fe8556c to b09451b Compare July 26, 2026 13:55
@renovate
renovate Bot force-pushed the develop/renovete-major-graphqlcodegenerator-monorepo branch from b09451b to f876c39 Compare July 30, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@corrupt952 corrupt952 Awaiting requested review from corrupt952

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants