chore(deps): update graphqlcodegenerator monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-codegen/cli (source)	7.2.0 → 7.3.1
@graphql-codegen/plugin-helpers (source)	7.1.0 → 7.2.1

---

Release Notes

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

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.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: (in timezone Asia/Tokyo)

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