[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-codegen/cli (source)	7.4.0 → 7.4.1

---

Release Notes

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

v7.4.1

Compare Source

Patch Changes

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

  • Updated dependency
    @graphql-tools/code-file-loader@^8.1.39 ↗︎
    (from ^8.1.28, in dependencies)

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

  • Updated dependency
    @graphql-tools/merge@^9.2.4 ↗︎
    (from ^9.0.6, in dependencies)

• #​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.

---

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.

🔕 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: pnpm-lock.yaml

Error: ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION

  × installing dependencies
  ╰─▶ 1 lockfile entries failed verification:
        @types/node@24.13.4 was published at 2026-09-09T18:10:47.240Z, within
      the minimumReleaseAge cutoff (2026-09-09T17:50:25.500Z)
  help: The lockfile contains entries that the active policies reject. This
        can mean the lockfile is stale, or that someone committed a lockfile
        that bypassed the policy locally — inspect recent changes to pnpm-
        lock.yaml before trusting it. If the changes look expected, run "pnpm
        clean --lockfile" and then "pnpm install" to rebuild from a fresh
        resolution. Alternatively, relax the policy that flagged them.