lint-staged

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.

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.

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.

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.

Improve error logging when failing to read or parse a configuration file

Upgrade micromatch@4.0.7

Fix release issue with previous version; update dependencies

Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.

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.

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.

Update lilconfig@3.0.0

Update most dependencies

Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Suppress some warnings when using the "--quiet" flag

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.

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.

Drop support for Node.js 14

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

dependencies: update most dependencies

Detect duplicate redundant braces in pattern

dependencies: update listr2@6.6.0

dependencies: replace colorette with chalk for better color support detection

Use index-based stash references for improved MSYS2 compatibility

Version bump only

Expose cli entrance from "lint-staged/bin"

Remove support for Node.js 12

lint-staged will no longer support Node.js 12, which is EOL since 30 April 2022

deps: update execa@^6.1.0