Update dependency lint-staged to v12.5.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lint-staged	12.3.7 -> 12.5.0

---

Release Notes

okonet/lint-staged (lint-staged)

v12.5.0

Compare Source

Bug Fixes

• include all files when using --config <path> (641d1c2)
• skip backup stash when using the --diff option (d4da24d)

Features

• add --diff-filter option for overriding list of (staged) files (753ef72)
• add --diff option for overriding list of (staged) files (35fcce9)

v12.4.3

Compare Source

Bug Fixes

• deps: downgrade yaml@1.10.2 to support Node.js 12 (383a96e)
• deps: update commander@^9.2.0 (22ebf52)
• deps: update yaml@^2.0.1 (ec73af0)

v12.4.2

Compare Source

Bug Fixes

• correctly handle --max-arg-length cli option (1db5f26)

v12.4.1

Compare Source

Bug Fixes

• correctly handle symlinked config files (b3f63ec)

v12.4.0

Compare Source

Bug Fixes

• handle empty input by returning empty array from parseGitZOutput (a118817)
• limit configuration discovery to cwd (d8fdf1d)
• restore functionality of parent globs for a single configuration file (877ab4c)

Features

• expose --max-arg-length cli option (e8291b0)

v12.3.8

Compare Source

Bug Fixes

• avoid passing unexpected arguments from forEach to process.kill() (1b1f0e4)
• clear execution interruption interval on first catch (46952cb)

---

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 this update again.

---

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

---

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

[renovate]

⚠ 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

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @destinationstransfers/eslint-plugin@2.9.190
npm ERR! Found: eslint@8.46.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"8.46.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from @typescript-eslint/utils@5.60.1
npm ERR!     node_modules/@typescript-eslint/utils
npm ERR!       @typescript-eslint/utils@"5.60.1" from @typescript-eslint/eslint-plugin@5.60.1
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         dev @typescript-eslint/eslint-plugin@"5.60.1" from the root project
npm ERR!       1 more (@typescript-eslint/type-utils)
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from eslint@8.46.0
npm ERR!   15 more (@typescript-eslint/eslint-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^6.6.0 || ^7.0.0" from @destinationstransfers/eslint-plugin@2.9.190
npm ERR! node_modules/@destinationstransfers/eslint-plugin
npm ERR!   dev @destinationstransfers/eslint-plugin@"2.9.190" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^6.6.0 || ^7.0.0" from @destinationstransfers/eslint-plugin@2.9.190
npm ERR!   node_modules/@destinationstransfers/eslint-plugin
npm ERR!     dev @destinationstransfers/eslint-plugin@"2.9.190" 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/worker/b7ebfa/3c0613/cache/others/npm/_logs/2023-07-29T23_08_02_630Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/b7ebfa/3c0613/cache/others/npm/_logs/2023-07-29T23_08_02_630Z-debug-0.log