Releases: lint-staged/lint-staged
v15.2.10
v15.2.9
v15.2.8
Patch Changes
-
f0480f0Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version switched the--show-toplevelflag with--show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_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
Patch Changes
- #1440
a51be80Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version drops the--path-format=absoluteoption to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggitto the latest version.
v15.2.6
v15.2.5
Patch Changes
-
#1424
31a1f95Thanks @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
91abea0Thanks @iiroj! - Improve error logging when failing to read or parse a configuration file -
#1424
ee43f15Thanks @iiroj! - Upgrade [email protected]
v15.2.4
v15.2.3
v15.2.2
v15.2.1
Patch Changes
- #1387
e4023f6Thanks @iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdinof the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdinis ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.