Update dependency lint-staged to v16 #195

renovate · 2025-05-10T18:05:52Z

This PR contains the following updates:

Package	Change	Age	Confidence
lint-staged	`10.5.4` -> `16.2.6`

Release Notes

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

`v16.2.6`

Compare Source

Patch Changes

#1693 33d4502 Thanks @Adrian-Baran-GY! - Fix problems with --continue-on-error option, where tasks might have still been killed (SIGINT) when one of them failed.

`v16.2.5`

Compare Source

Patch Changes

#1687 9e02d9d Thanks @iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn, lint-staged also failed and the backup stash might not have been automatically restored.

`v16.2.4`

Compare Source

Patch Changes

#1682 0176038 Thanks @iiroj! - Update dependencies, including nano-spawn@2.0.0 with bug fixes.
#1671 581a54e Thanks @iiroj! - Speed up execution by only importing the yaml depedency if using YAML configuration files.

`v16.2.3`

Compare Source

Patch Changes

#1669 27cd541 Thanks @iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

`v16.2.2`

Compare Source

Patch Changes

#1667 699f95d Thanks @iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

% npx lint-staged --fail-on-changes
✔ Backed up original state in git stash (c18d55a3)
✔ Running tasks for staged files...
✖ Tasks modified files and --fail-on-changes was used!
↓ Cleaning up temporary files...

✖ lint-staged failed because `--fail-on-changes` was used.

Any lost modifications can be restored from a git stash:

  > git stash list --format="%h %s"
  c18d55a3 On main: lint-staged automatic backup
  > git apply --index c18d55a3

`v16.2.1`

Compare Source

Patch Changes

#1664 8277b3b Thanks @iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @outslept!
```
export default {
---  "*": (files: string[]) => void console.log('staged files', files)
+++  "*": (files: readonly string[]) => void console.log('staged files', files)
}
```
#1654 70b9af3 Thanks @iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.
#1659 4996817 Thanks @iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.
#1654 7021f0a Thanks @iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

`v16.2.0`

Compare Source

Minor Changes

#1615 99eb742 Thanks @iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made by tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.
#1611 cd05fd3 Thanks @rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.
#1637 82fcc07 Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.
#1647 a5ecc06 Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging
#1636 8db2717 Thanks @iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

Thanks to @ItsNickBarry for the idea and initial implementation in #1552.
#1648 7900b3b Thanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes

#1633 7f9e485 Thanks @dependabot! - Bumps listr2 from 9.0.3 to 9.0.4.
#1626 99d5a9b Thanks @iiroj! - Due to recent phishing attacks, for example chalk@5.6.1 was released with malware. To avoid lint-staged's users being at risk the direct dependencies are pinned to exact versions, instead of allowing future patch versions with the caret (^) range.
#1588 035bbf2 Thanks @outslept! - Increase performance by listing staged files and searching for configuration concurrently.
#1645 deba3ad Thanks @iiroj! - Remove chalk as a dependency due to recent malware issue; read more at chalk/chalk#656.

If you are having trouble with ANSI color codes when using lint-staged, you can try setting either FORCE_COLOR=true or NO_COLOR=true env variables.

`v16.1.6`

Compare Source

Patch Changes

#1610 e93578e Thanks @iiroj! - Try to improve terminating of subprocess of tasks by using SIGKILL, and only calling pidtree when the the main task process has a known pid.

`v16.1.5`

Compare Source

Patch Changes

#1608 4e3ce22 Thanks @srsatt! - Detect the git repo's top-level directory correctly when in a worktree.

`v16.1.4`

Compare Source

Patch Changes

#1604 90b37b0 Thanks @iiroj! - Add another types field to package.json to make even more sure NPM detects that lint-staged includes built-in TypeScript type definitions.

`v16.1.3`

Compare Source

Patch Changes

#1602 7ea700b Thanks @dword-design! - Add the types field to package.json to make sure NPM detects lint-staged includes built-in TypeScript type definitions.

`v16.1.2`

Compare Source

Patch Changes

#1570 a7c0c88 Thanks @ItsNickBarry! - When using --diff-filter with the D option to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from git add like fatal: pathspec 'deleted-file' did not match any files.
38f942e Thanks @iiroj! - Removed an extraneous log entry that printed shouldHidePArtiallyStagedFiles to console output.

`v16.1.1`

Compare Source

Patch Changes

#1565 3686977 Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.
#1571 02299a9 Thanks @iiroj! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files.
#1563 bc61c74 Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

`v16.1.0`

Compare Source

Minor Changes

#1536 e729daa Thanks @iiroj! - A new flag --no-revert has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.
#1550 b27fa3f Thanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.

Patch Changes

#1558 c37dc38 Thanks @iiroj! - The minimum required Node.js version is lowered to 20.17 following nano-spawn@1.0.2.

`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.

`v15.5.1`

Compare Source

Patch Changes

#1533 5d53534 Thanks @iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:
```
✖ Failed to get staged files!
```

`v15.5.0`

Compare Source

Minor Changes

#1526 630af5f Thanks @iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.

Example with Prettier

By default Prettier prefers double quotes.

Previously

Stage file.js with only double quotes " changed to '
Run git commit -am "I don't like double quotes"
Lint-staged runs prettier --write file.js, converting all the ' back to "
Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
Commit was not done, original state is restored and single quotes ' are staged

Now

Stage file.js with only double-quotes " changed to '
Run git commit -am "I don't like double quotes"
Lint-staged runs prettier --write file.js, converting all the ' back to "
Because there are now no changes, lint-staged fails and cancels the commit
Commit was not done, and there are no staged changes

`v15.4.3`

Compare Source

Patch Changes

#1512 cbfed1d Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

`v15.4.2`

Compare Source

Patch Changes

#1509 8827ebf Thanks @iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

`v15.4.1`

Compare Source

Patch Changes

#1504 1c7a45e Thanks @iiroj! - Default TypeScript config filenames match JS equivalents.
#1504 9cc18c9 Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.

`v15.4.0`

Compare Source

Minor Changes

#1500 a8ec1dd Thanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:
```
/**
 * @&#8203;filename: lint-staged.config.js
 * @&#8203;type {import('lint-staged').Configuration}
 */
export default {
  '*': 'prettier --write',
}
```
It's also possible to use the .ts file extension for the configuration if your Node.js version supports it. The --experimental-strip-types flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.
```
export NODE_OPTIONS="--experimental-strip-types"

npx lint-staged --config lint-staged.config.ts
```

Patch Changes

#1501 9b79364 Thanks @iiroj! - Handle possible failures when logging user shell for debug info.

`v15.3.0`

Compare Source

Minor Changes

#1495 e69da9e Thanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.
#1493 fa0fe98 Thanks @iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

For example:
```
% npx lint-staged
✔ Backed up original state in git stash (20addf8)
✔ Running tasks for staged files...
✔ Applying modifications from tasks...
✔ Cleaning up temporary files...
```
where the backup can be seen with git show 20addf8, or git stash list:
```
% git stash list
stash@{0}: lint-staged automatic backup (20addf8)
```

`v15.2.11`

Compare Source

Patch Changes

#1484 bcfe309 Thanks @wormsik! - Escape paths containing spaces when using the "shell" option.
#1487 7dd8caa Thanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

`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.

`v15.2.7`

Compare Source

Patch Changes

#1440 a51be80 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 drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

`v15.2.6`

Compare Source

Patch Changes

#1433 119adb2 Thanks @iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

`v15.2.5`

Compare Source

Patch Changes

#1424 31a1f95 Thanks @iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.
#1423 91abea0 Thanks @iiroj! - Improve error logging when failing to read or parse a configuration file
#1424 ee43f15 Thanks @iiroj! - Upgrade micromatch@4.0.7

`v15.2.4`

Compare Source

Patch Changes

4f4537a Thanks @iiroj! - Fix release issue with previous version; update dependencies

`v15.2.2`

Compare Source

Patch Changes

#1391 fdcdad4 Thanks @iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.

`v15.2.1`

Compare Source

Patch Changes

#1484 bcfe309 Thanks @wormsik! - Escape paths containing spaces when using the "shell" option.
#1487 7dd8caa Thanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

`v15.2.0`

Compare Source

Minor Changes

#1371 f3378be Thanks @iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.

Patch Changes

#1362 17bc480 Thanks @antonk52! - update lilconfig@3.0.0
#1368 7c55ca9 Thanks @iiroj! - Update most dependencies
#1368 777d4e9 Thanks @iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.
#1373 85eb0dd Thanks @iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

`v15.1.0`

Compare Source

Minor Changes

#1344 0423311 Thanks @danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

#1355 105d901 Thanks @iiroj! - Suppress some warnings when using the "--quiet" flag

`v15.0.2`

Compare Source

Patch Changes

#1339 8e82364 Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.

`v15.0.1`

Compare Source

Patch Changes

#1217 d2e6f8b Thanks @louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

`v15.0.0`

Compare Source

Major Changes

#1322 66b93aa Thanks @iiroj! - Require at least Node.js 18.12.0

This release drops support for Node.js 16, which is EOL after 2023-09-11.
Please upgrade your Node.js to the latest version.

Additionally, all dependencies have been updated to their latest versions.

`v14.0.1`

Compare Source

Bug Fixes

fix reading config from stdin, introduced in v14.0.0 (#1317) (fc3bfea)

`v14.0.0`

Compare Source

Features

drop support for Node.js 14 (#1312) (9da8777)

BREAKING CHANGES

Please upgrade your Node.js version to at least 16.14.0.

`v13.3.0`

Compare Source

Bug Fixes

dependencies: update most dependencies (7443870)
detect duplicate redundant braces in pattern (d895aa8)

Features

dependencies: update listr2@6.6.0 (09844ca)

`v13.2.3`

Compare Source

Bug Fixes

the --diff option implies --no-stash (66a716d)

`v13.2.2`

Compare Source

Bug Fixes

dependencies: update yaml@2.2.2 (GHSA-f9xv-q969-pqx4) (#1290) (cf691aa)

`v13.2.1`

Compare Source

Bug Fixes

ignore "package.json" as config file when it's invalid JSON (#1281) (e7ed6f7)

`v13.2.0`

Compare Source

Bug Fixes

dependencies: replace colorette with chalk for better color support detection (f598725)
use index-based stash references for improved MSYS2 compatibility (#1270) (60fcd99)