[deps]: Update lint-staged to v17

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
lint-staged	16.4.0 → 17.0.5

---

Release Notes

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

v17.0.5

Compare Source

Patch Changes

• #​1792 1f67271 - Correctly set the --max-arg-length default value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.

v17.0.4

Compare Source

Patch Changes

• #​1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

  • after editing <file> it is staged with git add <file>, and then committed with git commit
  • after editing <file> it is committed with git commit --all without explicit git add
  • after editing <file> it is committed with git commit <pathspec> without explicit git add

  There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

v17.0.3

Compare Source

Patch Changes

• #​1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
  • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
  • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

v17.0.2

Compare Source

Patch Changes

• #​1779 88670ca Thanks @​iiroj! - Enable immutable GitHub releases

v17.0.1

Compare Source

Patch Changes

• #​1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

v17.0.0

Compare Source

Major Changes

• #​1745 e244adf Thanks @​iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!

• #​1676 0584e0b Thanks @​outslept! - Lint-staged now tries to verify the installed Git version is at least 2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!

• #​1745 2dcc40a Thanks @​iiroj! - The dependency yaml is now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:

  npm install --development yaml

  If you're using .lintstagedrc as the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to .lintstagedrc.json to avoid needing to install yaml.

Minor Changes

• #​1748 809d5ef Thanks @​iiroj! - Add new option --hide-all for hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.

• #​1759 f13045a Thanks @​iiroj! - Update dependencies, including tinyexec@1.1.1 to fix the following issues:

  • When using a Node.js version manager with multiple versions installed (nvm, n, for example), scripts with the #!/usr/bin/env node shebang (Prettier, ESLint, for example) were previously spawned using the default Node.js version configured by the version manager (the one which node points to) on POSIX systems. Now, they will be spawned with the same version that lint-staged itself was started with.
    • For example, if your default Node.js version is 24.14.1 but lint-staged is run with the latest version 25.9.0, the tasks spawned by lint-staged will now also use version 25.9.0. Previously they were spawned using 24.14.1.
  • When installing Node.js from the Ubuntu App Center (Snap store), the node executable available in PATH is a symlink pointing to Snap itself. The sandboxing features of Snap prevented lint-staged from spawning scripts with the #!/usr/bin/env node shebang, because it meant lint-staged tried to spawn Snap via the symlink. This resulted in an ENOENT error when trying to run prettier, for example. Now, since the real node executable's directory is available in the PATH, lint-staged will instead spawn the script with the real node binary succesfully.

• #​1761 d3251b1 Thanks @​iiroj! - Lint-staged now runs git update-index --again after running tasks, instead of git add <originally staged files>. This should improve compatibility when using non-default indexes, for example when committing with a pathspec git commit -m "message" . instead of adding files to the index.

• #​1745 a9585ac Thanks @​iiroj! - Remove commander as a dependency and use the built-in parseArgs from node:util to parse CLI flags.

Patch Changes

• #​1755 c82d30b Thanks @​iiroj! - All tests now pass on the Bun runtime (latest).

• #​1750 a401818 Thanks @​iiroj! - Remove manual handling for git stash --keep-index resurrecting deleted files, because the issue was fixed in Git 2.23.0 and lint-staged requires at least Git 2.32.0.

• #​1771 c4b8936 Thanks @​iiroj! - Fix documentation about multiple config files and the --cwd option. When using it, all tasks will be run in the specified directory. For example, to run everything in the actual process.cwd(), use lint-staged --cwd=".".

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every 2nd week starting on the 2 week of the year before 4am on Monday"
• 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.

[cloudflare-workers-and-pages]

Deploying contributing-docs with    Cloudflare Pages

Latest commit:	c675204
Status:	✅  Deploy successful!
Preview URL:	https://9626c71f.contributing-docs.pages.dev
Branch Preview URL:	https://renovate-lint-staged-17-x.contributing-docs.pages.dev

View logs

[bitwarden-bot]

Internal tracking:

• ID: PM-38088
• Link: https://bitwarden.atlassian.net/browse/PM-38088

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: REQUEST CHANGES

Automated Renovate PR bumping lint-staged from 16.4.0 to 17.0.5 — a major version bump. Only manifest (package.json) and package-lock.json changes are present; lock file is consistent with the manifest update. The lint-staged configuration in this repo is inline JSON in package.json, so the v17 change making yaml an optional dependency does not affect this project. The primary concern is a Node.js engines mismatch introduced by this bump.

Code Review Details

• ⚠️ : lint-staged@17 requires Node >=22.22.1, but engines.node is pinned to ~22.14.0
  • package.json:50

Dependency Changes

Package	Change	Ecosystem
lint-staged	16.4.0 → 17.0.5 (major)	npm

[claude]

⚠️ IMPORTANT: lint-staged@17 requires Node >=22.22.1, but this project's engines.node is pinned to ~22.14.0 (i.e. 22.14.x).

Details and fix

The v17 release notes explicitly state: "Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1". The tilde range ~22.14.0 resolves to >=22.14.0 <22.15.0, which does not satisfy >=22.22.1. Any developer running the documented Node version (22.14.x) will:

• See an EBADENGINE warning on npm ci
• Have their pre-commit hook fail when husky invokes lint-staged (v17 performs a runtime Node version check)

CI passes today only because .nvmrc contains 22 (no minor pin), so the GitHub Actions runner resolves to the latest 22.x line (currently 22.22.3+).

Suggested fix: bump engines.node to a range compatible with the new lint-staged requirement, e.g.:

"engines": {
  "node": "~22.22.0",
  "npm": "~11.3.0"
}

Reference: lint-staged v17.0.0 release notes