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 linters (major) #130

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint (source) ^8.57.0 -> ^9.0.0 age adoption passing confidence
eslint-config-love ^43.1.0 -> ^47.0.0 age adoption passing confidence
eslint-plugin-n ^16.6.2 -> ^17.0.0 age adoption passing confidence

Release Notes

eslint/eslint (eslint)

v9.0.0

Compare Source

mightyiam/eslint-config-love (eslint-config-love)

v47.0.0

Compare Source

⚠ BREAKING CHANGES
  • no longer provides env nor globals.
Features
  • do not specify env nor globals (53802ac)

v46.0.0

Compare Source

⚠ BREAKING CHANGES
  • (trying to) specify all options for rules that are used.
    Most likely will not affect you.
Features
Testing
  • exported value deep equality (c869c59)

v45.0.0

Compare Source

⚠ BREAKING CHANGES
  • all rule configs are arrays.
    This is a breaking change only if you are importing and processing the
    exported value yourself. Otherwise, this shouldn't affect you. Sorry for
    the major bump. Just being careful.
Features
  • all rule configs are arrays (9738761)
Refactoring
  • no extend from eslint-config-standard (065ce30)
Testing
  • rule todo list for eslint core & all plugins (8c84a0e)

v44.0.0

Compare Source

⚠ BREAKING CHANGES
Build system / dependencies
  • ci: "ci" job explicitly fails if test matrix fails (7dddb49)
  • ci: ci workflow if not cancelled (43b73e8)
  • ci: release from branch main (03a84a5)
  • nix: replace flake.nix with shell.nix (023d0b0)
  • shell.nix: nodejs_latest (75d18a0)
  • shell.nix: typescript-language-server (662a8f4)
Features
Testing
  • expected resolved config rules (593ac1b)
eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.2.1

Compare Source

🩹 Fixes
🧹 Chores

v17.2.0

Compare Source

🌟 Features
  • no-missing-imports: add tryExtensions option (#​228) (ae5329c)
  • no-unsupported-features: ✨ Update to node v20.12.0/v21.7.0 (#​229) (a8d0539)
🩹 Fixes

v17.1.0

Compare Source

🌟 Features
📚 Documentation

v17.0.0

Compare Source

Chores
  • use ts-ignore-import to lighten the dependencies (#​219) (fb0aaae)

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate. View repository job log here.


Thanks for the PR!

Deployments, as required, will be available below:

Please create PRs in draft mode. Mark as ready to enable:

After merge, new images are deployed in:

@renovate renovate bot requested a review from mishraomp as a code owner April 22, 2024 14:28
@renovate renovate bot enabled auto-merge (squash) April 22, 2024 14:28
@renovate renovate bot requested a review from DerekRoberts as a code owner April 22, 2024 14:28
Copy link
Contributor Author

renovate bot commented Apr 22, 2024

⚠ Artifact update problem

Renovate failed to update artifacts 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: frontend/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/eslint
npm ERR!   dev eslint@"^9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   @typescript-eslint/parser@"^7.0.1" from [email protected]
npm ERR!   node_modules/eslint-config-love
npm ERR!     dev eslint-config-love@"^47.0.0" from the root project
npm ERR!   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     peer @typescript-eslint/eslint-plugin@"^7.0.1" from [email protected]
npm ERR!     node_modules/eslint-config-love
npm ERR!       dev eslint-config-love@"^47.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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-22T15_17_56_511Z-eresolve-report.txt

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

File name: backend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @typescript-eslint/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^9.0.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm ERR!     node_modules/@typescript-eslint/utils
npm ERR!       @typescript-eslint/utils@"7.3.1" from @typescript-eslint/[email protected]
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         dev @typescript-eslint/eslint-plugin@"^7.0.0" from the root project
npm ERR!       1 more (@typescript-eslint/type-utils)
npm ERR!     @eslint-community/eslint-utils@"^4.1.2" from [email protected]
npm ERR!     node_modules/eslint-plugin-es-x
npm ERR!       eslint-plugin-es-x@"^7.5.0" from [email protected]
npm ERR!       node_modules/eslint-plugin-n
npm ERR!         dev eslint-plugin-n@"^17.0.0" from the root project
npm ERR!     2 more (eslint, eslint-plugin-n)
npm ERR!   5 more (eslint-compat-utils, eslint-config-prettier, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev @typescript-eslint/eslint-plugin@"^7.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"^7.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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-22T15_18_07_244Z-eresolve-report.txt

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

auto-merge was automatically disabled April 22, 2024 15:27

Pull request was closed

@DerekRoberts DerekRoberts deleted the renovate/major-linters branch April 22, 2024 15:27
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.

1 participant