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 typescript-eslint monorepo to v8.3.0 #2887

Merged
merged 1 commit into from
Aug 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 25, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@typescript-eslint/eslint-plugin (source) 8.2.0 -> 8.3.0 age adoption passing confidence
@typescript-eslint/parser (source) 8.2.0 -> 8.3.0 age adoption passing confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.3.0

Compare Source

🚀 Features
  • eslint-plugin: [no-deprecation] add rule
🩹 Fixes
  • eslint-plugin: [no-unnecessary-template-expression] add missing parentheses in autofix

  • eslint-plugin: [no-unnecessary-type-parameters] check mapped alias type arguments

  • utils: add TSDeclareFunction to functionTypeTypes

  • ast-spec: use Expression in argument of ThrowStatement

❤️ Thank You
  • Abraham Guo
  • Daichi Kamiyama
  • Josh Goldberg ✨
  • Kim Sang Du
  • Sukka
  • Vida Xie

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.3.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.


Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 changed the title chore(deps): update typescript-eslint monorepo to v8.2.0 chore(deps): update typescript-eslint monorepo to v8.2.0 - autoclosed Aug 25, 2024
@renovate renovate bot closed this Aug 25, 2024
@renovate renovate bot deleted the renovate/typescript-eslint-monorepo branch August 25, 2024 07:03
@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v8.2.0 - autoclosed chore(deps): update typescript-eslint monorepo to v8.2.0 Aug 26, 2024
@renovate renovate bot reopened this Aug 26, 2024
@renovate renovate bot restored the renovate/typescript-eslint-monorepo branch August 26, 2024 19:30
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from 40aed98 to 44431f8 Compare August 26, 2024 19:31
@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v8.2.0 chore(deps): update typescript-eslint monorepo to v8.3.0 Aug 26, 2024
Copy link
Contributor Author

renovate bot commented Aug 26, 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 could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.9.1" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error     @eslint-community/eslint-utils@"^4.1.2" from [email protected]
npm error     node_modules/eslint-plugin-es-x
npm error       eslint-plugin-es-x@"^7.5.0" from [email protected]
npm error       node_modules/eslint-plugin-n
npm error         dev eslint-plugin-n@"17.10.2" from the root project
npm error     2 more (eslint-plugin-n, @typescript-eslint/utils)
npm error   10 more (eslint-compat-utils, eslint-config-prettier, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8" from [email protected]
npm error node_modules/eslint-plugin-import
npm error   dev eslint-plugin-import@"2.29.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8" from [email protected]
npm error   node_modules/eslint-plugin-import
npm error     dev eslint-plugin-import@"2.29.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-08-28T01_52_26_093Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-28T01_52_26_093Z-debug-0.log

@renovate renovate bot enabled auto-merge (squash) August 28, 2024 01:52
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from 44431f8 to 4142ab1 Compare August 28, 2024 01:52
@renovate renovate bot merged commit 4876e25 into main Aug 28, 2024
0 of 14 checks passed
@renovate renovate bot deleted the renovate/typescript-eslint-monorepo branch August 28, 2024 01:52
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