chore(deps): update dependency lint-staged to v15.2.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lint-staged	15.2.7 -> 15.2.10

---

Release Notes

lint-staged/lint-staged (lint-staged)

v15.2.10

Compare Source

Patch Changes

• #​1471 e3f283b Thanks @​iiroj! - Update minor dependencies, including micromatch@~4.0.8.

v15.2.9

Compare Source

Patch Changes

• #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes

• f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

  The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.

[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: yarn.lock

error SyntaxError: Invalid value type 349:0 in /tmp/renovate/repos/github/NodeBB/nodebb-plugin-openai/yarn.lock
    at Parser.unexpected (/opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:64026:11)
    at Parser.parse (/opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:64154:16)
    at Parser.parse (/opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:64131:26)
    at parse (/opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:64231:21)
    at module.exports.exports.default (/opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:63793:96)
    at Function.<anonymous> (/opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:3068:63)
    at Generator.next (<anonymous>)
    at step (/opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:310:30)
    at /opt/containerbase/tools/yarn-slim/1.22.22/20.17.0/node_modules/yarn/lib/cli.js:321:13