-
Notifications
You must be signed in to change notification settings - Fork 5
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.2.10 #30
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/lint-staged-15.x-lockfile
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #30 +/- ##
=======================================
Coverage 95.04% 95.04%
=======================================
Files 5 5
Lines 101 101
Branches 33 33
=======================================
Hits 96 96
Misses 5 5 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
from
February 25, 2024 10:34
950ce84
to
9bd6c19
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
from
May 21, 2024 23:56
9bd6c19
to
1c91039
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.2
chore(deps): update dependency lint-staged to v15.2.4
May 21, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
from
May 25, 2024 13:11
1c91039
to
08fd461
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.4
chore(deps): update dependency lint-staged to v15.2.5
May 25, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
from
June 4, 2024 13:47
08fd461
to
c128297
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.5
chore(deps): update dependency lint-staged to v15.2.6
Jun 11, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
2 times, most recently
from
June 12, 2024 20:52
727931a
to
aa5ccd1
Compare
renovate
bot
changed the title
chore(deps): update dependency lint-staged to v15.2.6
chore(deps): update dependency lint-staged to v15.2.7
Jun 12, 2024
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
from
July 21, 2024 15:08
aa5ccd1
to
fb78d48
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
from
August 3, 2024 09:12
fb78d48
to
4f1de98
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 3, 2024
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-lockfile
branch
from
August 13, 2024 08:34
4f1de98
to
9e893e7
Compare
renovate
bot
force-pushed
the
renovate/lint-staged-15.x-lockfile
branch
from
August 28, 2024 11:17
9e893e7
to
8cb352b
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-lockfile
branch
from
September 1, 2024 20:34
8cb352b
to
64f29f7
Compare
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.1
->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 [email protected]v15.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.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.