-
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
build(deps): update dependency lint-staged to ^15.3.0 #100
Open
renovate
wants to merge
1
commit into
default
Choose a base branch
from
renovate/lint-staged-15.x
base: default
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
May 28, 2024 11:27
412f4c6
to
5ba855b
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.4
build(deps): update dependency lint-staged to ^15.2.5
May 28, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
June 14, 2024 19:28
5ba855b
to
644c477
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.5
build(deps): update dependency lint-staged to ^15.2.6
Jun 14, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
June 15, 2024 19:43
644c477
to
093b4b7
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.6
build(deps): update dependency lint-staged to ^15.2.7
Jun 15, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 6, 2024 07:33
093b4b7
to
4fdc305
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.7
build(deps): update dependency lint-staged to ^15.2.8
Aug 6, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
August 16, 2024 06:13
4fdc305
to
38f65a0
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.8
build(deps): update dependency lint-staged to ^15.2.9
Aug 16, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
September 4, 2024 16:43
38f65a0
to
350215c
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.9
build(deps): update dependency lint-staged to ^15.2.10
Sep 4, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 13, 2024 16:44
350215c
to
26fe610
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.10
build(deps): update dependency lint-staged to ^15.2.11
Dec 13, 2024
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/lint-staged-15.x
branch
from
December 31, 2024 14:07
26fe610
to
933d8c8
Compare
renovate
bot
changed the title
build(deps): update dependency lint-staged to ^15.2.11
build(deps): update dependency lint-staged to ^15.3.0
Dec 31, 2024
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.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 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 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.