-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update dependency lint-staged from v13.3.0 to v15 #192
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/lint-staged-15.x
base: master
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
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
November 11, 2023 18:54
5039d4a
to
d20eda2
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 3, 2023 20:39
d20eda2
to
8d24e93
Compare
Visit the preview URL for this PR (updated for commit fd8115f): https://ent-ninsar-dev--pr192-renovate-lint-staged-20nc2zqk.web.app (expires Fri, 20 Dec 2024 03:10:47 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 459be81c3496ac31e0d1abe75517fb8af6c796be |
renovate
bot
changed the title
Update dependency lint-staged from v13.2.3 to v15
Update dependency lint-staged from v13.3.0 to v15
Dec 10, 2023
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
December 11, 2023 02:10
f71db2b
to
2c0ca9b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
January 3, 2024 00:03
3a10dee
to
f5397ae
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
January 18, 2024 06:29
f5397ae
to
52e5b15
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
February 5, 2024 15:59
d3729b8
to
25c0f69
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
February 21, 2024 06:49
3c2631b
to
09c77b7
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
March 14, 2024 00:05
09c77b7
to
4d17801
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
April 4, 2024 03:48
4d17801
to
df1ca3c
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
April 12, 2024 03:53
df1ca3c
to
9cc05b5
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
May 7, 2024 08:10
d61241c
to
a926edc
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
May 17, 2024 06:49
0d64fdb
to
5de79f2
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
May 25, 2024 12:39
07c8034
to
4e8a05a
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
May 31, 2024 03:06
d219334
to
0a326d7
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
4 times, most recently
from
June 18, 2024 01:56
779c01c
to
c2d1786
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
July 12, 2024 01:28
a6335ad
to
fddeb1a
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 3, 2024 09:10
fddeb1a
to
1f7cf50
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 13, 2024 08:25
1f7cf50
to
4aae6cb
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
September 4, 2024 03:36
d303098
to
fa1f1de
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
3 times, most recently
from
September 21, 2024 01:23
abf718e
to
047d2e6
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
September 28, 2024 06:02
047d2e6
to
274843d
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
4 times, most recently
from
October 18, 2024 00:52
d775cf6
to
fdb7f0b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
October 24, 2024 01:22
f050a7e
to
3bdcb64
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
November 2, 2024 03:58
8cd70f2
to
dde57b3
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
November 15, 2024 04:58
8bbd4a9
to
03b121c
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
December 4, 2024 04:30
69c031e
to
aa8130a
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 10, 2024 16:41
aa8130a
to
7623cfd
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 13, 2024 03:08
7623cfd
to
fd8115f
Compare
Quality Gate passedIssues Measures |
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.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 micromatch@4.0.7v15.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 lilconfig@3.0.0#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.