-
Notifications
You must be signed in to change notification settings - Fork 84
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 #428
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-code-style-deps
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/major-code-style-deps
branch
from
August 3, 2023 21:25
5ddb815
to
9b095d0
Compare
renovate
bot
changed the title
chore(deps): update dependency prettier to v3
chore(deps): update code style deps (major)
Aug 14, 2023
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
3 times, most recently
from
August 17, 2023 23:20
4505d5a
to
9c043c5
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
August 22, 2023 01:20
30ba125
to
fac4f0f
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
August 31, 2023 22:29
c1dcfd9
to
c96bbe2
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
September 27, 2023 21:51
c96bbe2
to
e334ac6
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
October 25, 2023 21:35
1e5e4f6
to
578ea61
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
November 22, 2023 22:59
6fb3e10
to
e3c208f
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
December 6, 2023 22:03
e3c208f
to
20c10ef
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
December 13, 2023 23:46
20c10ef
to
58da961
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
January 18, 2024 00:30
58da961
to
8c814f7
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
January 31, 2024 23:16
8c814f7
to
24e40ca
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
February 8, 2024 00:31
24e40ca
to
40d61a7
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
April 6, 2024 21:45
40d61a7
to
35b66db
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
April 24, 2024 21:40
5e17764
to
6af430f
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
May 4, 2024 21:17
6af430f
to
ef57bef
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
May 12, 2024 04:00
1c8aec0
to
0e32214
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
3 times, most recently
from
May 25, 2024 22:07
4a94d1e
to
988a45a
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
June 5, 2024 22:01
988a45a
to
5e58ac6
Compare
This PR is missing a Jira ticket reference in the title or description. |
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
June 15, 2024 21:05
ac8e740
to
ffc864d
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
June 29, 2024 21:08
37b52a5
to
830aa6a
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
July 13, 2024 21:13
088de54
to
a03189d
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
August 3, 2024 21:13
9f0f28e
to
82ee6b8
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
3 times, most recently
from
August 14, 2024 21:56
3ecc0ca
to
d6b4eac
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
August 24, 2024 22:41
d6b4eac
to
ff17947
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
September 7, 2024 21:54
ec2a8b6
to
46bbef1
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
September 25, 2024 23:22
e5120a6
to
9566bf0
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
October 5, 2024 22:43
9566bf0
to
db362a8
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
October 19, 2024 21:33
db362a8
to
3756828
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
November 3, 2024 01:43
3756828
to
b2825c9
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
November 16, 2024 22:50
b2825c9
to
ba7e8f1
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
November 30, 2024 22:42
bfde74a
to
3f1b473
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
December 5, 2024 00:53
3f1b473
to
d2cc0b8
Compare
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
2 times, most recently
from
December 15, 2024 00:17
e581d10
to
b33bd3a
Compare
renovate
bot
changed the title
chore(deps): update code style deps (major)
chore(deps): update dependency lint-staged to v15
Dec 21, 2024
renovate
bot
force-pushed
the
renovate/major-code-style-deps
branch
from
December 29, 2024 02:04
b33bd3a
to
e53eac0
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.3.0
Release Notes
lint-staged/lint-staged (lint-staged)
v15.3.0
Compare Source
Minor Changes
#1495
e69da9e
Thanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.#1493
fa0fe98
Thanks @iiroj! - Added more help messages around the automaticgit stash
that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.For example:
where the backup can be seen with
git show 20addf8
, orgit stash list
: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 - "before 6am on Thursday,before 10am on Sunday" in timezone Europe/Kiev, 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.