chore(deps): update dependency lint-staged to v16

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lint-staged	^15.0.0 -> ^16.0.0

---

Release Notes

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

v16.0.0

Compare Source

Major Changes

• #​1546 158d15c Thanks @​iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them with node, especially when using Windows:

  {
    "*.js": "node my-js-linter.js"
  }

• #​1546 158d15c Thanks @​iiroj! - The --shell flag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via "$@​":

v15.5.2

Compare Source

Patch Changes

• #​1544 5561321 Thanks @​YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames.

---

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

! Corepack is about to download https://repo.yarnpkg.com/4.7.0/packages/yarnpkg-cli/bin/yarn.js
/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:22058
    throw new Error(
          ^

Error: Server answered with HTTP 429 when performing the request to https://repo.yarnpkg.com/4.7.0/packages/yarnpkg-cli/bin/yarn.js; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:22058:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async fetchUrlStream (/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:22081:20)
    at async download (/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:22204:18)
    at async installVersion (/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:22296:55)
    at async Engine.ensurePackageManager (/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:22847:32)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:22958:25)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.32.0/22.15.1/node_modules/corepack/dist/lib/corepack.cjs:23648:7)

Node.js v22.15.1