chore(deps): update devdependency lint-staged to v15 #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
96f4f1f
to
1f402d6
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
1f402d6
to
623db3b
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml |
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
623db3b
to
64f305f
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
e1ea0a9
to
893471f
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
893471f
to
bd5053e
Compare
|
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
bd5053e
to
9108083
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
1fe81d6
to
15bab94
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
15bab94
to
34cc523
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
34cc523
to
eeb3d7b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
eeb3d7b
to
bd03937
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^13.0.2->^15.2.10Release Notes
lint-staged/lint-staged (lint-staged)
v15.2.10Compare Source
Patch Changes
e3f283bThanks @iiroj! - Update minor dependencies, includingmicromatch@~4.0.8.v15.2.9Compare Source
Patch Changes
b69ce2dThanks @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.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 [email protected]v15.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 [email protected]#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" flagv15.0.2Compare Source
Patch Changes
8e82364Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.v15.0.1Compare Source
Patch Changes
d2e6f8bThanks @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.0Compare Source
Major Changes
#1322
66b93aaThanks @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.1Compare Source
Bug Fixes
v14.0.0Compare Source
Features
BREAKING CHANGES
16.14.0.v13.3.0Compare Source
Bug Fixes
Features
listr2@​6.6.0(09844ca)v13.2.3Compare Source
Bug Fixes
--diffoption implies--no-stash(66a716d)v13.2.2Compare Source
Bug Fixes
[email protected](GHSA-f9xv-q969-pqx4) (#1290) (cf691aa)v13.2.1Compare Source
Bug Fixes
v13.2.0Compare Source
Bug Fixes
colorettewithchalkfor better color support detection (f598725)Features
v13.1.4Compare Source
v13.1.3Compare Source
v13.1.2Compare Source
Bug Fixes
v13.1.1Compare Source
Bug Fixes
--stashwhen using the--diffoption (99390c3)v13.1.0Compare Source
Features
v13.0.4Compare Source
Bug Fixes
v13.0.3Compare Source
Bug Fixes
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.