codeowners-generator
codeowners-generator copied to clipboard
chore(deps): update dependency lint-staged to v15
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| lint-staged | 13.0.3 -> 15.2.10 |
Release Notes
lint-staged/lint-staged (lint-staged)
v15.2.10
Patch Changes
v15.2.9
Patch Changes
- #1463
b69ce2dThanks @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
Patch Changes
-
f0480f0Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version switched the--show-toplevelflag 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
Patch Changes
- #1440
a51be80Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version drops the--path-format=absoluteoption to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggitto the latest version.
v15.2.6
Patch Changes
- #1433
119adb2Thanks @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
Patch Changes
-
#1424
31a1f95Thanks @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
91abea0Thanks @iiroj! - Improve error logging when failing to read or parse a configuration file -
#1424
ee43f15Thanks @iiroj! - Upgrade [email protected]
v15.2.4
Patch Changes
v15.2.2
Patch Changes
- #1391
fdcdad4Thanks @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
Patch Changes
- #1387
e4023f6Thanks @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 thestdinof the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdinis 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
Minor Changes
- #1371
f3378beThanks @iiroj! - Using the--no-stashflag 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-stagedthat is automatically enabled when--no-stashis used.
Patch Changes
-
#1362
17bc480Thanks @antonk52! - update [email protected] -
#1368
777d4e9Thanks @iiroj! - To improve performance, only uselilconfigwhen 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
85eb0ddThanks @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
Minor Changes
- #1344
0423311Thanks @danielbayley! - Add support for loading configuration frompackage.yamlandpackage.ymlfiles, supported bypnpm.
Patch Changes
v15.0.2
Patch Changes
- #1339
8e82364Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.
v15.0.1
Patch Changes
- #1217
d2e6f8bThanks @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
Major Changes
-
#1322
66b93aaThanks @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
Bug Fixes
v14.0.0
Features
BREAKING CHANGES
- Please upgrade your Node.js version to at least
16.14.0.
v13.3.0
Bug Fixes
- dependencies: update most dependencies (7443870)
- detect duplicate redundant braces in pattern (d895aa8)
Features
- dependencies: update
listr2@​6.6.0(09844ca)
v13.2.3
Bug Fixes
- the
--diffoption implies--no-stash(66a716d)
v13.2.2
Bug Fixes
- dependencies: update
[email protected](GHSA-f9xv-q969-pqx4) (#1290) (cf691aa)
v13.2.1
Bug Fixes
v13.2.0
Bug Fixes
- dependencies: replace
colorettewithchalkfor better color support detection (f598725) - use index-based stash references for improved MSYS2 compatibility (#1270) (60fcd99)
Features
v13.1.4
v13.1.3
v13.1.2
Bug Fixes
v13.1.1
Bug Fixes
- allow re-enabling
--stashwhen using the--diffoption (99390c3)
v13.1.0
Features
v13.0.4
Bug Fixes
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Pull Request Test Coverage Report for Build 10366615033
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 100.0%
| Totals | |
|---|---|
| Change from base Build 8489311769: | 0.0% |
| Covered Lines: | 266 |
| Relevant Lines: | 266 |
💛 - Coveralls
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 100.00%. Comparing base (
64d7089) to head (3ad3cc6).
:exclamation: Current head 3ad3cc6 differs from pull request most recent head 417beef
Please upload reports for the commit 417beef to get more accurate results.
Additional details and impacted files
@@ Coverage Diff @@
## master #375 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 11 11
Lines 287 287
Branches 67 67
=========================================
Hits 287 287
| Flag | Coverage Δ | |
|---|---|---|
| unittests | 100.00% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.