-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency lint-staged to v15 #182
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/lint-staged-15.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
October 15, 2023 17:00
d9039d6
to
c82e8cf
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
October 19, 2023 11:15
c82e8cf
to
2c0f222
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
November 11, 2023 15:29
2c0f222
to
6ae3007
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 2, 2023 06:21
6ae3007
to
8df299b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 3, 2023 18:30
8df299b
to
c6c87f1
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
January 5, 2024 00:57
c6c87f1
to
99786e3
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
January 31, 2024 09:47
99786e3
to
2209a60
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
February 5, 2024 15:51
2209a60
to
f67caaf
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
February 6, 2024 01:24
f67caaf
to
2fcd83f
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
February 7, 2024 18:10
2fcd83f
to
fb2f65b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
February 25, 2024 12:18
fb2f65b
to
8fa1d8b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
March 18, 2024 02:36
8fa1d8b
to
15de6fb
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
March 19, 2024 19:20
15de6fb
to
720bebc
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
March 21, 2024 03:04
720bebc
to
0e69d85
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
May 22, 2024 04:11
0e69d85
to
0157efe
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
May 25, 2024 12:55
0157efe
to
e0a82e6
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
June 11, 2024 18:46
e0a82e6
to
1a5337c
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
June 12, 2024 19:54
1a5337c
to
b095f66
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 3, 2024 07:51
b095f66
to
8d21666
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 4, 2024 01:36
8d21666
to
2237832
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 13, 2024 07:05
2237832
to
b79079a
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
September 2, 2024 00:55
b79079a
to
b62d0f5
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
September 18, 2024 07:53
b62d0f5
to
41dcfba
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
September 18, 2024 10:17
41dcfba
to
b3ab0a5
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
November 26, 2024 17:42
b3ab0a5
to
b1afb88
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.3.0
->15.2.10
Release Notes
lint-staged/lint-staged (lint-staged)
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
.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.