emmercm / igir

πŸ•Ή A zero-setup ROM collection manager that sorts, filters, extracts or archives, patches, and reports on collections of any size on any OS.
https://igir.io/
GNU General Public License v3.0
363 stars 18 forks source link

Chore: update dependency eslint-config-airbnb-typescript to v18 - abandoned #1052

Closed renovate[bot] closed 6 months ago

renovate[bot] commented 6 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-airbnb-typescript 17.1.0 -> 18.0.0 age adoption passing confidence

Release Notes

iamturns/eslint-config-airbnb-typescript (eslint-config-airbnb-typescript) ### [`v18.0.0`](https://togithub.com/iamturns/eslint-config-airbnb-typescript/releases/tag/v18.0.0) [Compare Source](https://togithub.com/iamturns/eslint-config-airbnb-typescript/compare/v17.1.0...v18.0.0) ##### chore - upgrade to ts-eslint v7 ([#​334](https://togithub.com/iamturns/eslint-config-airbnb-typescript/issues/334)) ([b00dada](https://togithub.com/iamturns/eslint-config-airbnb-typescript/commit/b00dadaf88e4bf7afd133880478ebc5a8b3f712b)) ##### BREAKING CHANGES - Update [@​typescript-eslint](https://togithub.com/typescript-eslint) to v7 or above, and eslint to 8.56.0 or above

Configuration

πŸ“… Schedule: Branch creation - "on the 27th day of the month" in timezone America/Los_Angeles, 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 this update again.



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

renovate[bot] commented 6 months ago

⚠ 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:

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: igir@2.6.1
npm ERR! Found: @typescript-eslint/eslint-plugin@6.21.0
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/eslint-plugin@"^7.0.0" from eslint-config-airbnb-typescript@18.0.0
npm ERR! node_modules/eslint-config-airbnb-typescript
npm ERR!   dev eslint-config-airbnb-typescript@"18.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-03-27T07_18_17_244Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-27T07_18_17_244Z-debug-0.log
github-actions[bot] commented 6 months ago

:test_tube: Branch testing instructions

This pull request can be tested locally with the following command:

npm exec --yes -- "github:emmercm/igir#renovate/major-18-eslint" [commands..] [options]

Comment generated by the Pull Request Commenter workflow.

renovate[bot] commented 6 months ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

renovate[bot] commented 6 months ago

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

github-actions[bot] commented 5 months ago

:lock: Inactive pull request lock

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Comment generated by the GitHub Lock Issues workflow.