This PR contains the following updates:
Release Notes
lint-staged/lint-staged (lint-staged)
Compare Source
Patch Changes
f0480f0 Thanks@iiroj! - In the previous version the nativegit 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.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.
Compare Source
Patch Changes
- #1440
a51be80 Thanks@iiroj! - In the previous version the nativegit 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 upgradinggit to the latest version.
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.
Compare Source
Patch Changes
#142431a1f95 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.
#142391abea0 Thanks@iiroj! - Improve error logging when failing to read or parse a configuration file
#1424ee43f15 Thanks@iiroj! - Upgrade micromatch@4.0.7
Compare Source
Patch Changes
4f4537a Thanks@iiroj! - Fix release issue with previous version; update dependencies
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.
Compare Source
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 thestdin of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin 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.
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
#136217bc480 Thanks@antonk52! - update lilconfig@3.0.0
#13687c55ca9 Thanks@iiroj! - Update most dependencies
#1368777d4e9 Thanks@iiroj! - To improve performance, only uselilconfig 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.
#137385eb0dd Thanks@iiroj! - When determining git directory, usefs.realpath() only for symlinks. It looks likefs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.
Compare Source
Minor Changes
Patch Changes
Configuration
📅Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated byMend Renovate. View therepository job log.
This PR contains the following updates:
15.0.2->15.2.8Release Notes
lint-staged/lint-staged (lint-staged)
v15.2.8Compare Source
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.7Compare Source
Patch Changes
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.6Compare Source
Patch Changes
119adb2Thanks@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.5Compare Source
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 micromatch@4.0.7v15.2.4Compare Source
Patch Changes
4f4537aThanks@iiroj! - Fix release issue with previous version; update dependenciesv15.2.2Compare Source
Patch Changes
fdcdad4Thanks@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.1Compare Source
Patch Changes
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.v15.2.0Compare Source
Minor Changes
f3378beThanks@iiroj! - Using the--no-stashflag 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-stagedthat is automatically enabled when--no-stashis used.Patch Changes
#1362
17bc480Thanks@antonk52! - update lilconfig@3.0.0#1368
7c55ca9Thanks@iiroj! - Update most dependencies#1368
777d4e9Thanks@iiroj! - To improve performance, only uselilconfigwhen 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
85eb0ddThanks@iiroj! - When determining git directory, usefs.realpath()only for symlinks. It looks likefs.realpath()changes some Windows mapped network filepaths unexpectedly, causing issues.v15.1.0Compare Source
Minor Changes
0423311Thanks@danielbayley! - Add support for loading configuration frompackage.yamlandpackage.ymlfiles, supported bypnpm.Patch Changes
105d901Thanks@iiroj! - Suppress some warnings when using the "--quiet" flagConfiguration
📅Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated byMend Renovate. View therepository job log.