Update dependency @graphql-codegen/cli to v7.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-codegen/cli (source)	7.2.0 → 7.4.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

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• Branch creation
  • "after 2am and before 8am on friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: eesast-web@2024.0.0
npm error Found: graphql@17.0.2
npm error node_modules/graphql
npm error   graphql@"17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^15.0.0 || ^16.0.0" from @apollo/client@3.14.1
npm error node_modules/@apollo/client
npm error   @apollo/client@"3.14.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-04T00_37_40_269Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-04T00_37_40_269Z-debug-0.log

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request