forked from joedixon/nova-translation
-
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 to v15 #195
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.
Open
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
6 times, most recently
from
October 21, 2023 02:17
e2b15a4
to
fffd580
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
4 times, most recently
from
October 27, 2023 13:26
0b9cd50
to
2f01b78
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
November 4, 2023 03:36
2f01b78
to
a491926
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
November 18, 2023 05:10
b2bb1fd
to
9e8f88c
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
5 times, most recently
from
December 3, 2023 21:08
f3d5211
to
7ca8696
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 16, 2023 04:56
7ca8696
to
68a200d
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
3 times, most recently
from
December 29, 2023 04:47
58a3c2b
to
70c9d0d
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
3 times, most recently
from
January 9, 2024 22:20
9fd6834
to
264733e
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
January 13, 2024 04:02
a0e013f
to
b800ba1
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
February 5, 2024 16:39
8fe619f
to
03d24aa
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
May 25, 2024 13:15
d8f7245
to
f5c23c8
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
June 12, 2024 17:42
b878887
to
3c06764
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
7 times, most recently
from
July 24, 2024 14:55
a5a11f7
to
3241ce2
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 3, 2024 09:56
3241ce2
to
38eb5b5
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 13, 2024 09:01
38eb5b5
to
8aa8711
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
2 times, most recently
from
September 1, 2024 16:57
1635823
to
994779b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
September 25, 2024 16:39
994779b
to
89d7c05
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
4 times, most recently
from
October 30, 2024 07:29
7d76ade
to
b01404e
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
October 30, 2024 09:45
b01404e
to
a86c1d7
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.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 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 is behind base branch, 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.