-
Notifications
You must be signed in to change notification settings - Fork 1
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.3 #10
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
|
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 13, 2024 06:07
0d21dfb
to
15eb5c6
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
September 1, 2024 15:27
15eb5c6
to
05167a0
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
December 10, 2024 16:14
05167a0
to
72361e0
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 28, 2024 12:29
72361e0
to
d08a8a8
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
January 16, 2025 09:00
d08a8a8
to
4f5f145
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 20:34
4f5f145
to
4e63e4f
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
changed the title
chore(deps): update dependency lint-staged to v15.4.1
chore(deps): update dependency lint-staged to v15.4.2
Jan 23, 2025
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
January 23, 2025 12:21
4e63e4f
to
d4bbd00
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
January 26, 2025 16:33
d4bbd00
to
5f09010
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.4.2
chore(deps): update dependency lint-staged to v15.4.3
Jan 26, 2025
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:
15.2.7
->15.4.3
Release Notes
lint-staged/lint-staged (lint-staged)
v15.4.3
Compare Source
Patch Changes
cbfed1d
Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.v15.4.2
Compare Source
Patch Changes
8827ebf
Thanks @iiroj! - Change lint-staged's dependencies to use caret (^
) ranges instead of tilde (~
). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.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.
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.