Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency graphql to v16 #167

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency graphql to v16 #167

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 8, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql 15.9.0 -> 16.9.0 age adoption passing confidence

Release Notes

graphql/graphql-js (graphql)

v16.9.0

Compare Source

v16.9.0 (2024-06-21)

New Feature 🚀
  • #​4119 backport[v16]: Introduce "recommended" validation rules (@​benjie)
  • #​4122 backport[v16]: Enable passing values configuration to GraphQLEnumType as a thunk (@​benjie)
  • #​4124 backport[v16]: Implement OneOf Input Objects via @oneOf directive (@​benjie)
Committers: 1

v16.8.2

Compare Source

v16.8.2 (2024-06-12)

Bug Fix 🐞* #​4022 fix: remove globalThis check and align with what bundlers can accept (@​JoviDeCroock)
Internal 🏠* #​4104 Fix publish scripts (@​benjie)
Committers: 2

v16.8.1

Compare Source

v16.8.1 (2023-09-19)
Bug Fix 🐞
Committers: 1

v16.8.0

Compare Source

v16.8.0 (2023-08-14)

New Feature 🚀
Committers: 1

v16.7.1

Compare Source

v16.7.1 (2023-06-22)

📢 Big shout out to @​phryneas, who managed to reproduce this issue and come up with this fix.

Bug Fix 🐞
Committers: 1

v16.7.0

Compare Source

v16.7.0 (2023-06-21)
New Feature 🚀
Bug Fix 🐞
Committers: 3

v16.6.0

Compare Source

v16.6.0 (2022-08-16)

New Feature 🚀
Bug Fix 🐞
Committers: 2

v16.5.0

Compare Source

v16.5.0 (2022-05-09)

New Feature 🚀
Committers: 1

v16.4.0

Compare Source

v16.4.0 (2022-04-25)

New Feature 🚀
Bug Fix 🐞
Docs 📝
2 PRs were merged
Polish 💅
3 PRs were merged
Internal 🏠
26 PRs were merged
Dependency 📦
2 PRs were merged
Committers: 7

v16.3.0

Compare Source

v16.3.0 (2022-01-26)

New Feature 🚀
Bug Fix 🐞
Docs 📝
2 PRs were merged
Polish 💅
7 PRs were merged
Internal 🏠
5 PRs were merged
Dependency 📦
4 PRs were merged
Committers: 6

v16.2.0: v16.2.0

Compare Source

v16.2.0 (2021-12-17)

New Feature 🚀
Docs 📝
Polish 💅
Internal 🏠
2 PRs were merged
Committers: 2

v16.1.0

Compare Source

v16.1.0 (2021-12-07)

New Feature 🚀
Bug Fix 🐞
Docs 📝
Polish 💅
9 PRs were merged
Internal 🏠
9 PRs were merged
Dependency 📦
4 PRs were merged
Committers: 5

v16.0.1

Compare Source

v16.0.1 (2021-11-01)

Bug Fix 🐞
Polish 💅
Internal 🏠
Committers: 1

v16.0.0

Compare Source

v16.0.0 (2021-10-28)

Breaking Change 💥
Deprecation ⚠
New Feature 🚀
Bug Fix 🐞
Docs 📝
5 PRs were merged
Polish 💅
119 PRs were merged

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Updates to dependencies label Sep 8, 2022
@renovate renovate bot requested a review from sgarner September 8, 2022 06:17
@renovate
Copy link
Contributor Author

renovate bot commented Sep 8, 2022 •
edited
Loading

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev @typescript-eslint/eslint-plugin@"6.0.0" from the root project
npm ERR!   peerOptional @typescript-eslint/eslint-plugin@"^5.0.0" from [email protected]
npm ERR!   node_modules/eslint-plugin-jest
npm ERR!     dev eslint-plugin-jest@"26.9.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @typescript-eslint/eslint-plugin@"6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   peer @typescript-eslint/parser@"^6.0.0 || ^6.0.0-alpha" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-02-18T01_02_12_304Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-18T01_02_12_304Z-debug-0.log

@renovate renovate bot force-pushed the renovate/graphql-16.x branch 2 times, most recently from c23a971 to 6c155c0 Compare May 13, 2023 19:11
@renovate renovate bot force-pushed the renovate/graphql-16.x branch 2 times, most recently from 704ab1d to 9883a5a Compare May 25, 2023 20:11
@renovate renovate bot force-pushed the renovate/graphql-16.x branch 4 times, most recently from 0ae88c6 to 478869a Compare June 27, 2023 20:30
@renovate renovate bot force-pushed the renovate/graphql-16.x branch 2 times, most recently from 3b0c583 to 0eb3b1f Compare August 3, 2023 05:10
@renovate renovate bot force-pushed the renovate/graphql-16.x branch 2 times, most recently from 57d8605 to 3b89c8c Compare August 17, 2023 22:53
@renovate renovate bot force-pushed the renovate/graphql-16.x branch 2 times, most recently from e53d326 to 7c5da07 Compare October 30, 2023 12:36
@renovate renovate bot force-pushed the renovate/graphql-16.x branch 2 times, most recently from b2eeb89 to 6628ed0 Compare December 3, 2023 14:58
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 15, 2024 •
edited
Loading

⚠️ 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.5.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.13.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.13.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-24T20_42_01_798Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-24T20_42_01_798Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sgarner sgarner Awaiting requested review from sgarner

Assignees
No one assigned
Labels
dependencies Updates to dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants