Skip to content

Update dependency graphql to v17#661

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

Update dependency graphql to v17#661
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/graphql-17.x

Conversation

@renovate

@renovate renovate Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
graphql 16.14.217.0.1 age confidence

Release Notes

graphql/graphql-js (graphql)

v17.0.1

Compare Source

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: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • 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 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

renovate Bot commented Jun 16, 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 stop working in the next 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-angular@13.0.0
npm error Found: graphql@17.0.1
npm error node_modules/graphql
npm error   graphql@"17.0.1" from the root project
npm error   peer graphql@"^16.0.0 || ^17.0.0" from @apollo/client@4.2.3
npm error   node_modules/@apollo/client
npm error     @apollo/client@"4.2.3" from the root project
npm error     peer @apollo/client@"^4.0.1" from apollo-angular@13.0.0
npm error     node_modules/apollo-angular
npm error       apollo-angular@"13.0.0" from the root project
npm error   1 more (@graphql-typed-document-node/core)
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^16.0.0" from apollo-angular@13.0.0
npm error node_modules/apollo-angular
npm error   apollo-angular@"13.0.0" from the root project
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-angular@13.0.0
npm error   node_modules/apollo-angular
npm error     apollo-angular@"13.0.0" 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-06-23T01_11_39_801Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-23T01_11_39_801Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/graphql-17.x branch 5 times, most recently from b8c27f7 to 86a51db Compare June 20, 2026 05:59
@renovate renovate Bot force-pushed the renovate/graphql-17.x branch from 86a51db to e51343e Compare June 23, 2026 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants