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.21.0 #14468

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 21, 2025

This PR contains the following updates:

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

Release Notes

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

v8.21.0

Compare Source

🩹 Fixes
  • eslint-plugin: [no-duplicate-enum-values] handle template literal (#​10675)
  • eslint-plugin: [no-base-to-string] don't crash for recursive array or tuple types (#​10633)
  • eslint-plugin: [no-for-in-array] report on any type which may be an array or array-like (#​10535)
  • eslint-plugin: check JSX spread elements for misused spread usage (#​10653)
  • eslint-plugin: [no-unnecessary-type-arguments] handle type args on jsx (#​10630)
❤️ Thank You

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

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

v8.21.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.

typescript-eslint/typescript-eslint (typescript-eslint)

v8.21.0

Compare Source

This was a version bump only for typescript-eslint 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 is behind base branch, 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 added the dependencies Pull requests that update a dependency file label Jan 21, 2025
Copy link
Contributor Author

renovate bot commented Jan 21, 2025

⚠️ 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 warn ERESOLVE overriding peer dependency
npm warn While resolving: @apollo/[email protected]
npm warn Found: [email protected]
npm warn node_modules/graphql-ws
npm warn   graphql-ws@"6.0.1" from @nestjs/[email protected]
npm warn   node_modules/@nestjs/graphql
npm warn     dev @nestjs/graphql@"13.0.1" from the root project
npm warn     1 more (@nestjs/apollo)
npm warn
npm warn Could not resolve dependency:
npm warn peerOptional graphql-ws@"^5.5.5" from @apollo/[email protected]
npm warn node_modules/@apollo/client
npm warn   optional @apollo/client@"~3.2.5 || ~3.3.0 || ~3.4.0 || ~3.5.0 || ~3.6.0 || ~3.7.0 || ~3.8.0 || ~3.9.0 || ~3.10.0 || ~3.11.0 || ~3.12.0" from [email protected]
npm warn   node_modules/graphql-tools
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/graphql-ws
npm warn   peerOptional graphql-ws@"^5.5.5" from @apollo/[email protected]
npm warn   node_modules/@apollo/client
npm warn     optional @apollo/client@"~3.2.5 || ~3.3.0 || ~3.4.0 || ~3.5.0 || ~3.6.0 || ~3.7.0 || ~3.8.0 || ~3.9.0 || ~3.10.0 || ~3.11.0 || ~3.12.0" from [email protected]
npm warn     node_modules/graphql-tools
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/graphql
npm error   dev graphql@"16.9.0" from the root project
npm error   peer graphql@"14.x || 15.x || 16.x" from @apollo/[email protected]
npm error   node_modules/@apollo/cache-control-types
npm error     @apollo/cache-control-types@"^1.0.3" from @apollo/[email protected]
npm error     node_modules/@apollo/server
npm error       dev @apollo/server@"4.11.3" from the root project
npm error       2 more (...)
npm error   24 more (@apollo/client, @apollo/server, ...)
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^16.10.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/apollo
npm error   dev @nestjs/apollo@"13.0.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/graphql
npm error   peer graphql@"^16.10.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/apollo
npm error     dev @nestjs/apollo@"13.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/2025-01-21T09_28_24_994Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-21T09_28_24_994Z-debug-0.log

@coveralls
Copy link

Pull Request Test Coverage Report for Build c74e249a-6670-4884-bd0c-34ac303dc358

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.696%

Totals Coverage Status
Change from base Build 04141477-ef45-4554-9983-0d2ccac4c33d: 0.0%
Covered Lines: 7103
Relevant Lines: 7919

💛 - Coveralls

@kamilmysliwiec kamilmysliwiec merged commit 73b9232 into master Jan 21, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants