chore(deps): update dependency lint-staged to v15 #294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
10.5.4
->15.2.11
Release Notes
lint-staged/lint-staged (lint-staged)
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
e3f283b
Thanks @iiroj! - Update minor dependencies, includingmicromatch@~4.0.8
.v15.2.9
Compare Source
Patch Changes
b69ce2d
Thanks @iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected
.v15.2.8
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.
v15.2.7
Compare Source
Patch Changes
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.v15.2.6
Compare Source
Patch Changes
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 [email protected]v15.2.4
Compare Source
Patch Changes
4f4537a
Thanks @iiroj! - Fix release issue with previous version; update dependenciesv15.2.2
Compare Source
Patch Changes
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
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.v15.2.0
Compare Source
Minor Changes
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 [email protected]#1368
7c55ca9
Thanks @iiroj! - Update most dependencies#1368
777d4e9
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.#1373
85eb0dd
Thanks @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.0
Compare Source
Minor Changes
0423311
Thanks @danielbayley! - Add support for loading configuration frompackage.yaml
andpackage.yml
files, supported bypnpm
.Patch Changes
105d901
Thanks @iiroj! - Suppress some warnings when using the "--quiet" flagv15.0.2
Compare Source
Patch Changes
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
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.0This 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
v14.0.0
Compare Source
Features
BREAKING CHANGES
16.14.0
.v13.3.0
Compare Source
Bug Fixes
Features
listr2@​6.6.0
(09844ca)v13.2.3
Compare Source
Bug Fixes
--diff
option implies--no-stash
(66a716d)v13.2.2
Compare Source
Bug Fixes
[email protected]
(GHSA-f9xv-q969-pqx4) (#1290) (cf691aa)v13.2.1
Compare Source
Bug Fixes
v13.2.0
Compare Source
Bug Fixes
colorette
withchalk
for better color support detection (f598725)Features
v13.1.4
Compare Source
v13.1.3
Compare Source
v13.1.2
Compare Source
Bug Fixes
v13.1.1
Compare Source
Bug Fixes
--stash
when using the--diff
option (99390c3)v13.1.0
Compare Source
Features
v13.0.4
Compare Source
Bug Fixes
v13.0.3
Compare Source
Bug Fixes
v13.0.2
Compare Source
Bug Fixes
--diff
and--diff-filter
options when checking task modifications (1a5a66a)v13.0.1
Compare Source
Bug Fixes
process.kill
when killing tasks on failure (f2c6bdd)Performance Improvements
EventsEmitter
instead ofsetInterval
for killing tasks on failure (c508b46)v13.0.0
Compare Source
Bug Fixes
execa@^6.1.0
(659c85c)yaml@^2.1.1
(2750a3d)Features
BREAKING CHANGES
lint-staged
will no longer support Node.js 12, which is EOL since 30 April 2022v12.5.0
Compare Source
Bug Fixes
--config <path>
(641d1c2)--diff
option (d4da24d)Features
--diff-filter
option for overriding list of (staged) files (753ef72)--diff
option for overriding list of (staged) files (35fcce9)v12.4.3
Compare Source
Bug Fixes
v12.4.2
Compare Source
Bug Fixes
v12.4.1
Compare Source
Bug Fixes
v12.4.0
Compare Source
Bug Fixes
parseGitZOutput
(a118817)Features
--max-arg-length
cli option (e8291b0)v12.3.8
Compare Source
Bug Fixes
v12.3.7
Compare Source
Bug Fixes
--silent
andFORCE_COLOR
settings (d327873)v12.3.6
Compare Source
Bug Fixes
v12.3.5
Compare Source
Bug Fixes
v12.3.4
Compare Source
Bug Fixes
package.json
to exports (#1059) (3395150)v12.3.3
Compare Source
Bug Fixes
v12.3.2
Compare Source
Bug Fixes
v12.3.1
Compare Source
Bug Fixes
v12.3.0
Compare Source
Features
--cwd
option for overriding task directory (62b5b83)v12.2.2
Compare Source
Bug Fixes
cwd
first (4afcda5)v12.2.1
Compare Source
Bug Fixes
v12.2.0
Compare Source
Bug Fixes
Features
v12.1.7
Compare Source
Bug Fixes
v12.1.6
Compare Source
Bug Fixes
v12.1.5
Compare Source
Bug Fixes
--debug
option enables debug mode (5cceeb6)v12.1.4
Compare Source
Bug Fixes
v12.1.3
Compare Source
Bug Fixes
v12.1.2
Compare Source
Bug Fixes
v12.1.1
Compare Source
Bug Fixes
v12.1.0
Compare Source
Features
.js
config file with ESM syntax (410c3ba)cosmiconfig
withlilconfig
+yaml
to reduce dependencies (e7f9fa0).mjs
config (8d3b176)v12.0.3
Compare Source
Bug Fixes
enquirer
(e01585f)v12.0.2
Compare Source
Bug Fixes
npm
version requirement (#1047) (e50d6d4)v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Features
BREAKING CHANGES
requires Node.js version
^12.20.0 || ^14.13.1 || >=16.0.0
.To update your Node.js integration, please use:
v11.2.6
Compare Source
Bug Fixes
cosmiconfig
fromlilconfig
(#1035) (e035b80), closes #1033 #981v11.2.5
Compare Source
Bug Fixes
js-yaml
to fix yaml config loading (#1033) (612d806)v11.2.4
Compare Source
Performance Improvements
cosmiconfig
withlilconfig
(#981) (04529e2)v11.2.3
Compare Source
Bug Fixes
v11.2.2
Compare Source
Bug Fixes
v11.2.1
Compare Source
Bug Fixes
v11.2.0
Compare Source
Features
v11.1.4
Compare Source
v11.1.3
Compare Source
v11.1.2
Compare Source
Bug Fixes
v11.1.1
Compare Source
Bug Fixes
v11.1.0
Compare Source
Features
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING 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 by Mend Renovate. View the repository job log.