Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Sep 9, 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 Confidence
@graphql-codegen/cli (source) 5.0.7 → 7.4.1 age confidence
@graphql-codegen/typescript (source) 4.1.6 → 6.1.0 age confidence
@graphql-codegen/typescript-graphql-request (source) 6.3.0 → 7.1.0 age confidence
@graphql-codegen/typescript-operations (source) 4.6.1 → 6.1.6 age confidence

Release Notes

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

v7.4.1

Compare Source

Patch Changes

  • #​10935
    fb1a7c4
    Thanks @​eddeee888! - dependencies updates:

  • #​10942
    57c3e7b
    Thanks @​eddeee888! - dependencies updates:

  • #​10942
    57c3e7b
    Thanks @​eddeee888! - Bump @graphql-tools/merge from ^9.0.6 to
    ^9.2.4.

  • #​10935
    fb1a7c4
    Thanks @​eddeee888! - Fix a Windows-specific import() failure on
    absolute paths when loading a schema/document from a .js/.cjs/.mjs file (via
    @graphql-tools/code-file-loader), and when loading modules passed to that loader's own require
    option. Node's dynamic import() rejects raw absolute Windows paths (the drive letter is parsed
    as a URL scheme). Fixed by bumping @graphql-tools/code-file-loader to 8.1.39, which contains
    the upstream fix
    (ardatan/graphql-tools#8421).

  • #​10936
    9521c0c
    Thanks @​eddeee888! - Fix watch mode's generated ignore glob
    patterns using the platform path separator (\ on Windows), which @parcel/watcher never
    matched, so generated output files were watched (and could re-trigger builds) instead of being
    ignored. Ignore patterns are now always forward-slash, as @parcel/watcher expects.

    Also fixes the test suite's TempDir.clean() helper on Windows, where rimraf.sync() rejected
    its own glob-style cleanup pattern as containing illegal path characters; now passes
    { glob: true }. This is a test-only change (tests/utils.ts is not part of the published
    package) included here since it was needed to get the suite green on Windows alongside the
    watch-mode fix.

v7.4.0

Compare Source

Minor Changes

  • #​10928
    90229a5
    Thanks @​eddeee888! - Add
    contentComparison?: 'cache-first' | 'disk' to control disk-vs-cache write comparison in watch
    mode.

    In watch mode the CLI caches the hash of the content it last wrote per file and compares new
    output against that cached hash to skip redundant writes. This assumes generated output is a pure
    function of the codegen inputs. An output whose content depends on the file's existing content
    (e.g. a preset that reads the file and rewrites part of it) breaks that assumption: if the file is
    changed on disk and codegen regenerates content identical to a previous run, the cached hash still
    matches and the write is skipped, so the on-disk change is never corrected.

    contentComparison: 'disk' opts an output into comparing the generated content against the file
    on disk instead of the in-memory record of what codegen last wrote, so the file is rewritten when
    it was changed externally. It can be set:

    • by a preset, on the GenerateOptions it returns from buildGeneratesSection, or
    • on the output config (generates[output].contentComparison) for any output, including plain
      plugin outputs without a preset.

    When both are present, the preset's value takes precedence. The default, 'cache-first', keeps
    the existing in-memory-cache behaviour for outputs that are a pure function of their inputs.

Patch Changes

  • #​10930
    448431a
    Thanks @​eddeee888! - Fix overwrite being ignored for
    preset-based generates outputs.

    A generates entry that used a preset and set overwrite (e.g.
    overwrite: { removeStaleFiles: false }) had that setting silently ignored, so in watch mode its
    generated files could still be deleted as stale.

    The CLI resolved overwrite per generated file by looking the file's path up in
    config.generates. That fails for a preset: its generates entry is keyed by the preset's
    baseOutputDir, not by any generated file's path (and a preset can emit files outside that
    directory), and the lookup additionally required a plugins key that preset entries don't have.
    Both cases fell through to the global config.overwrite (default true).

  • Updated dependencies
    [90229a5,
    448431a]:

v7.3.1

Compare Source

Patch Changes

  • #​10924
    0c8f5ba
    Thanks @​eddeee888! - Fix profiler output not being written to the
    filesystem in watch mode (--profile --watch)

    The profiler trace was only written on the non-watch code path, after the watch-mode early return,
    so a profiled watch session never produced a codegen-*.json file.

    The profiler now writes a fresh trace file after the initial run and after every rebuild, with
    each file containing only that run's events. A failed rebuild does not produce a trace and its
    events are discarded so they don't leak into the next successful run.

    The Profiler now owns its own trace lifecycle:

    • a new clear() method starts a new trace
    • a new outputName property provides the filename for the current trace (null for the noop
      profiler)
    • filename generation was removed from CodegenContext

  • Updated dependencies
    [0c8f5ba]:

v7.3.0

Compare Source

Minor Changes

  • #​10921
    58cdb31
    Thanks @​eddeee888! - Extend overwrite with
    overwrite.removeStaleFiles and overwrite.updateExistingFiles

    overwrite was being used to both remove stale files in watch mode and update existing files.
    Some plugins such as Server Preset may dynamically return files to write between watch runs (for
    performance purposes).

    The overwrite can now take an object with overwrite.removeStaleFiles and
    overwrite.updateExistingFiles fields to allow granular control over actions.

    This is not a breaking change because overwrite=true|false still works.

Patch Changes

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)

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

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the renovate label Sep 9, 2025
@changeset-bot

changeset-bot Bot commented Sep 9, 2025 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 720f58a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from ade1599 to f99e57b Compare October 5, 2025 16:35
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f99e57b to 208e1f8 Compare October 21, 2025 21:10
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 36049ec to 0e46044 Compare November 16, 2025 23:53
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 0e46044 to 79c3026 Compare November 20, 2025 14:07
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 79c3026 to f8f0d76 Compare November 29, 2025 05:25
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f8f0d76 to c2b3e5b Compare December 18, 2025 13:50
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from c2b3e5b to 1e50ad2 Compare December 31, 2025 14:46
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1e50ad2 to 68096c8 Compare January 11, 2026 12:53
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 68096c8 to 83b8900 Compare February 2, 2026 19:13
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 8a8f10d to 07b1109 Compare February 18, 2026 14:41
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 07b1109 to 6ef6083 Compare February 22, 2026 17:12
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 5 times, most recently from 43f4cd7 to 20af662 Compare March 13, 2026 11:45
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 20af662 to 4939845 Compare March 26, 2026 18:04
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 0158575 to 7a9b04e Compare April 19, 2026 08:34
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from dc05f0d to d3a5ac7 Compare May 6, 2026 18:28
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d3a5ac7 to 3a428a7 Compare May 9, 2026 13:29
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 3a428a7 to 388a9c1 Compare May 18, 2026 19:40
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from bf40610 to cd86d2b Compare June 2, 2026 15:01
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 3139628 to 0445b31 Compare June 16, 2026 17:58
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 0445b31 to b95edb7 Compare June 24, 2026 18:48
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from b95edb7 to 52f7d55 Compare July 6, 2026 20:09
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0046008 to b0524de Compare July 23, 2026 15:51
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 5c4e13d to 6d9bb0d Compare August 5, 2026 16:06
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 583d28c to 6319bce Compare August 14, 2026 20:40
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from feb312a to 92f3b65 Compare August 23, 2026 18:26
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 232e93d to d12314f Compare September 7, 2026 17:43
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d12314f to 720f58a Compare September 10, 2026 23:25
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

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants