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

Deps: Update dependency @types/node to v22. #255

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 22.9.0 -> 22.10.2 age adoption passing confidence

  • If you want to rebase/retry this PR, check this box

This PR has been generated on behalf of Nordcom AB by Renovate Bot.

Copy link
Contributor Author

renovate bot commented Nov 20, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @nordcom/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.7.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.0.1" from [email protected]
npm error node_modules/eslint-plugin-github
npm error   dev eslint-plugin-github@"5.0.1" 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-12-11T10_56_10_406Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-11T10_56_10_406Z-debug-0.log

@renovate renovate bot added the Dependency label Nov 20, 2024
@renovate renovate bot force-pushed the deps/bot-node-22.x branch 6 times, most recently from 19b14ef to 90bbf03 Compare November 28, 2024 07:23
@renovate renovate bot force-pushed the deps/bot-node-22.x branch 3 times, most recently from b223e33 to bab3794 Compare December 6, 2024 07:49
@renovate renovate bot force-pushed the deps/bot-node-22.x branch from bab3794 to a84a4d0 Compare December 11, 2024 10:56
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