[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-codegen/typescript-react-apollo (source)	4.4.2 → 6.0.1

---

Release Notes

dotansimha/graphql-code-generator-community (@​graphql-codegen/typescript-react-apollo)

v6.0.1

Compare Source

Patch Changes

• #​1717
  828f1de
  Thanks @​eddeee888! - Support GraphQL v17, where AST nodes leave
  variableDefinitions, directives and arguments undefined instead of an empty array.

v6.0.0

Compare Source

Major Changes

• #​1706
  54de5c2
  Thanks @​eddeee888! - Update @graphql-codegen/plugin-helpers and
  @graphql-codegen/visitor-plugin-common to v8. validate now reads outputFile from the info
  object passed as its fourth argument, so it requires @graphql-codegen/cli v8.

  The graphql peer dependency range is now ^16.0.0 || ^17.0.0, and engines.node is now
  >=22.18.0.

Patch Changes

• #​1706
  54de5c2
  Thanks @​eddeee888! - dependencies updates:
  • Updated dependency
    @graphql-codegen/plugin-helpers@^8.0.0 ↗︎
    (from ^6.3.0, in dependencies)
  • Updated dependency
    @graphql-codegen/visitor-plugin-common@^8.0.0 ↗︎
    (from ^7.2.2, in dependencies)
  • Updated dependency
    graphql@^16.0.0 || ^17.0.0 ↗︎ (from
    ^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0,
    in peerDependencies)

v5.0.0

Compare Source

Major Changes

• #​1530
  73ecb79
  Thanks @​wassim-k! - Update GraphQL Codegen common packages to
  latest (@graphql-codegen/visitor-plugin-common v7).

  This changes the shape of generated documents: a fragment's *Doc no longer interpolates the
  fragments it spreads, and each operation document instead interpolates every fragment it
  transitively spreads. Generated output is equivalent, but any code or snapshot asserting on the
  previous interpolation layout needs updating.

---

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-11-12T18_13_31_881Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-12T18_13_31_881Z-debug-0.log

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue). If it does not match the queue conditions yet, it enters the queue once it does.

• Queue this pull request