-
Notifications
You must be signed in to change notification settings - Fork 7
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.4.1 #399
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
July 5, 2024 13:51
83492a7
to
4f8be03
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
July 7, 2024 14:18
4f8be03
to
2ee22f0
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
July 7, 2024 15:44
2ee22f0
to
69a23c0
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
July 8, 2024 11:54
69a23c0
to
0137149
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
July 8, 2024 17:53
0137149
to
bdf18a7
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
July 9, 2024 09:07
bdf18a7
to
f234036
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 4, 2024 14:08
f234036
to
5818588
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.7
chore(deps): update dependency lint-staged to v15.2.8
Aug 4, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 4, 2024 15:54
5818588
to
337a165
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 8, 2024 10:19
337a165
to
eee586b
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 10, 2024 17:04
eee586b
to
04a01af
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 11, 2024 10:17
04a01af
to
28dc4c7
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 11, 2024 13:38
28dc4c7
to
8173e6c
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.8
chore(deps): update dependency lint-staged to v15.2.9
Aug 13, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 13, 2024 07:11
8173e6c
to
055d01d
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.9
chore(deps): update dependency lint-staged to v15.2.10
Sep 1, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
September 1, 2024 23:41
055d01d
to
c5a0125
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 10, 2024 15:09
c5a0125
to
d29cf53
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.10
chore(deps): update dependency lint-staged to v15.2.11
Dec 10, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 23, 2024 10:01
d29cf53
to
6e07658
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.11
chore(deps): update dependency lint-staged to v15.3.0
Dec 28, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 28, 2024 13:57
6e07658
to
fe04185
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.3.0
chore(deps): update dependency lint-staged to v15.4.0
Jan 16, 2025
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
January 16, 2025 08:40
fe04185
to
d4d907f
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.4.0
chore(deps): update dependency lint-staged to v15.4.1
Jan 16, 2025
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
January 16, 2025 21:11
d4d907f
to
6ed0d3a
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:
15.2.2
->15.4.1
Release Notes
lint-staged/lint-staged (lint-staged)
v15.4.1
Compare Source
Patch Changes
#1504
1c7a45e
Thanks @iiroj! - Default TypeScript config filenames match JS equivalents.#1504
9cc18c9
Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.v15.4.0
Compare Source
Minor Changes
#1500
a8ec1dd
Thanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:It's also possible to use the
.ts
file extension for the configuration if your Node.js version supports it. The--experimental-strip-types
flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.Patch Changes
9b79364
Thanks @iiroj! - Handle possible failures when logging user shell for debug info.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 dependenciesConfiguration
📅 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.