chore(deps): update graphqlcodegenerator monorepo

[ctison]

This PR contains the following updates:

Package	Type	Update	Change
@graphql-codegen/cli (source)	devDependencies	minor	7.2.0 → 7.4.0
@graphql-codegen/plugin-helpers (source)	dependencies	minor	7.1.0 → 7.3.0

---

Release Notes

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

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]:

  • @​graphql-codegen/plugin-helpers@7.3.0

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]:

  • @​graphql-codegen/plugin-helpers@7.2.1

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

• Updated dependencies
  [58cdb31]:
  • @​graphql-codegen/plugin-helpers@7.2.0

dotansimha/graphql-code-generator (@​graphql-codegen/plugin-helpers)

v7.3.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).

v7.2.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

v7.2.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.

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate CLI.

[Copilot]

🟡 Changes recommended

The updated lockfile introduces multiple graphql versions (CLI resolves to graphql@16.14.2 while the plugin package remains on graphql@17.0.2), which can break runtime schema/plugin interoperability in codegen.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the GraphQL Code Generator toolchain used by this monorepo (CLI at the workspace root and plugin helpers in the Golang plugin package), primarily to pull in upstream fixes and minor feature additions.

Changes:

• Bump @graphql-codegen/cli from 7.2.0 to 7.3.1.
• Bump @graphql-codegen/plugin-helpers in packages/graphql-codegen-golang from 7.1.0 to 7.2.1.
• Refresh pnpm-lock.yaml to reflect the updated dependency graph (including new peer resolutions).

File summaries

File	Description
pnpm-lock.yaml	Updates lock entries for the new @graphql-codegen/* versions and their resolved peer dependency tree.
packages/graphql-codegen-golang/package.json	Bumps plugin helper dependency used by the Golang codegen plugin package.
package.json	Bumps the root codegen CLI devDependency version.

Review details

Files not reviewed (1)

• pnpm-lock.yaml: Generated file

• Files reviewed: 2/3 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.