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

chore(deps): update dependency @tsconfig/node18 to v18.2.4 #2702

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 13, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tsconfig/node18 (source) 18.2.1 -> 18.2.4 age adoption passing confidence

Release Notes

tsconfig/bases (@​tsconfig/node18)

v18.2.4

Compare Source

v18.2.3

Compare Source

v18.2.2

Compare Source


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 renovate bot force-pushed the renovate/tsconfig-node18-18.x branch 2 times, most recently from 0539635 to f3b101a Compare October 12, 2023 16:30
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from f3b101a to 78ee579 Compare October 18, 2023 03:10
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from 78ee579 to c72eb04 Compare November 7, 2023 21:48
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from c72eb04 to 46d1fe7 Compare November 21, 2023 07:03
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from 46d1fe7 to daacffc Compare February 23, 2024 15:20
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch 2 times, most recently from d51089d to 66a6af0 Compare March 21, 2024 02:01
@renovate renovate bot changed the title chore(deps): update dependency @tsconfig/node18 to v18.2.2 chore(deps): update dependency @tsconfig/node18 to v18.2.3 Mar 24, 2024
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from 66a6af0 to 09f35aa Compare March 24, 2024 04:52
@renovate renovate bot changed the title chore(deps): update dependency @tsconfig/node18 to v18.2.3 chore(deps): update dependency @tsconfig/node18 to v18.2.4 Mar 27, 2024
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from 09f35aa to 9cb4046 Compare March 27, 2024 07:06
Copy link
Contributor Author

renovate bot commented May 5, 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: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.2.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.8.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.8.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-05-05T01_30_17_335Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-05T01_30_17_335Z-debug-0.log

@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from 9cb4046 to 4fa76be Compare May 5, 2024 01:30
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from 4fa76be to d3383e2 Compare August 1, 2024 06:22
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch 2 times, most recently from d591d1a to 60938c4 Compare August 28, 2024 01:51
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch 2 times, most recently from 19828f2 to 9592c0f Compare October 1, 2024 07:31
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from 9592c0f to eec5c05 Compare October 29, 2024 06:50
@renovate renovate bot changed the title chore(deps): update dependency @tsconfig/node18 to v18.2.4 chore(deps): update dependency @tsconfig/node18 to v18.2.4 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/tsconfig-node18-18.x branch December 8, 2024 18:53
@renovate renovate bot changed the title chore(deps): update dependency @tsconfig/node18 to v18.2.4 - autoclosed chore(deps): update dependency @tsconfig/node18 to v18.2.4 Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/tsconfig-node18-18.x branch from ade5d2d to eec5c05 Compare December 8, 2024 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

0 participants