Skip to content

chore(deps): update dependency graphql to v17 - #515

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/graphql-17.x
Open

chore(deps): update dependency graphql to v17#515
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/graphql-17.x

Conversation

@renovate

@renovate renovate Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
graphql 14.x || 15.x || 16.x14.x || 15.x || 16.x || 17.x age confidence
graphql 16.11.017.0.2 age confidence

Release Notes

graphql/graphql-js (graphql)

v17.0.2

Compare Source

v17.0.1

Compare Source

v17.0.1 (2026-06-16)
Bug Fix 🐞
  • #​4824 fix(diagnostics): emit asyncStart after promise settlement to match native tracePromise (@​logaretm)
Internal 🏠
2 PRs were merged
Committers: 2

v17.0.0

Compare Source

v17.0.0 (2026-06-15)
New Feature 🚀
Bug Fix 🐞
Docs 📝
11 PRs were merged
Polish 💅
2 PRs were merged
Internal 🏠
6 PRs were merged
Committers: 3

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 these updates 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
renovate Bot requested a review from a team as a code owner June 20, 2026 14:34
@renovate

renovate Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @apollo/client@4.0.9
npm error Found: graphql@17.0.2
npm error node_modules/graphql
npm error   dev graphql@"17.0.2" from the root project
npm error   peer graphql@"*" from @ardatan/relay-compiler@12.0.3
npm error   node_modules/@ardatan/relay-compiler
npm error     @ardatan/relay-compiler@"^12.0.3" from @graphql-tools/relay-operation-optimizer@7.0.19
npm error     node_modules/@graphql-tools/relay-operation-optimizer
npm error       @graphql-tools/relay-operation-optimizer@"^7.0.0" from @graphql-codegen/visitor-plugin-common@5.8.0
npm error       node_modules/@graphql-codegen/visitor-plugin-common
npm error         @graphql-codegen/visitor-plugin-common@"^5.8.0" from @graphql-codegen/client-preset@4.8.3
npm error         node_modules/@graphql-codegen/client-preset
npm error         4 more (@graphql-codegen/gql-tag-operations, ...)
npm error   34 more (@graphql-tools/apollo-engine-loader, ...)
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^16.0.0" from @apollo/client@4.0.9
npm error node_modules/@apollo/client
npm error   dev @apollo/client@"4.0.9" from the root project
npm error   peer @apollo/client@"^3.7.0 || ^4.0.0" from @apollo/generate-persisted-query-manifest@1.4.0
npm error   packages/generate-persisted-query-manifest
npm error     @apollo/generate-persisted-query-manifest@1.4.0
npm error     node_modules/@apollo/generate-persisted-query-manifest
npm error       workspace packages/generate-persisted-query-manifest from the root project
npm error   1 more (@apollo/persisted-query-lists)
npm error
npm error Conflicting peer dependency: graphql@16.14.2
npm error node_modules/graphql
npm error   peer graphql@"^16.0.0" from @apollo/client@4.0.9
npm error   node_modules/@apollo/client
npm error     dev @apollo/client@"4.0.9" from the root project
npm error     peer @apollo/client@"^3.7.0 || ^4.0.0" from @apollo/generate-persisted-query-manifest@1.4.0
npm error     packages/generate-persisted-query-manifest
npm error       @apollo/generate-persisted-query-manifest@1.4.0
npm error       node_modules/@apollo/generate-persisted-query-manifest
npm error         workspace packages/generate-persisted-query-manifest from the root project
npm error     1 more (@apollo/persisted-query-lists)
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-12T08_27_13_875Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-12T08_27_13_875Z-debug-0.log

@changeset-bot

changeset-bot Bot commented Jun 20, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: a183df5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/graphql-17.x branch from d8375f5 to f7288b9 Compare July 4, 2026 08:45
@renovate
renovate Bot force-pushed the renovate/graphql-17.x branch from f7288b9 to a183df5 Compare August 8, 2026 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants