Skip to content

Releases: lint-staged/lint-staged

v15.2.10

01 Sep 14:22
Compare
Choose a tag to compare

Patch Changes

v15.2.9

13 Aug 05:44
0ce5e14
Compare
Choose a tag to compare

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

03 Aug 06:32
52f6eef
Compare
Choose a tag to compare

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

12 Jun 17:28
87e4b30
Compare
Choose a tag to compare

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

11 Jun 16:40
Compare
Choose a tag to compare

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

25 May 11:05
Compare
Choose a tag to compare

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

21 May 19:16
8be6c8e
Compare
Choose a tag to compare

Patch Changes

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

v15.2.3

21 May 18:21
95d096d
Compare
Choose a tag to compare

Patch Changes

v15.2.2

05 Feb 14:26
Compare
Choose a tag to compare

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

31 Jan 07:45
Compare
Choose a tag to compare

Patch Changes

  • #1387 e4023f6 Thanks @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 the stdin of the spawned commands has accepted input, and essentially gotten stuck waiting. Now the stdin is 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.