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.

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

fix(deps): replace dependency apollo-server with @apollo/server #91

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 25, 2023

This PR contains the following updates:

Package Type Update Change
apollo-server (source) dependencies replacement ^3.4.1 -> ^4.0.0

This is a special PR that replaces apollo-server with the community suggested minimal stable replacement version.


Configuration

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

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

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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Jul 25, 2023

⚠ 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: apollo-server/v3/getting-started/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/graphql
npm ERR!   graphql@"^15.5.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^16.6.0" from @apollo/[email protected]
npm ERR! node_modules/@apollo/server
npm ERR!   @apollo/server@"^4.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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from 4087c29 to f775807 Compare July 27, 2023 16:29
@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from f775807 to 0e3367a Compare August 9, 2023 13:07
@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from 0e3367a to 2a905b8 Compare August 22, 2023 17:10
@renovate renovate bot changed the title fix(deps): replace dependency apollo-server with @apollo/server ^4.0.0 fix(deps): replace dependency apollo-server with @apollo/server Aug 30, 2023
@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from 2a905b8 to fe684fc Compare November 16, 2023 10:21
@renovate renovate bot requested a review from a team as a code owner November 16, 2023 10:21
@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from fe684fc to eb6bbba Compare January 1, 2024 11:36
@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from eb6bbba to 67dd24a Compare February 4, 2024 10:44
@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch 2 times, most recently from 3d31752 to 6b6f946 Compare April 25, 2024 11:01
Copy link
Contributor Author

renovate bot commented Jun 4, 2024

⚠️ 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: apollo-server/v3/getting-started/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/graphql
npm ERR!   graphql@"^15.5.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^16.6.0" from @apollo/[email protected]
npm ERR! node_modules/@apollo/server
npm ERR!   @apollo/server@"^4.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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from 6b6f946 to 25af2d6 Compare June 4, 2024 13:15
@renovate renovate bot force-pushed the renovate/getting-started-apollo-graphql-packages branch from 25af2d6 to b0abdf0 Compare August 28, 2024 07:53
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