Skip to content
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 #560

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 3, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 13.3.0 -> 15.3.0 age adoption passing confidence

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 automatic git 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:

    % npx lint-staged
    ✔ Backed up original state in git stash (20addf8)
    ✔ Running tasks for staged files...
    ✔ Applying modifications from tasks...
    ✔ Cleaning up temporary files...
    

    where the backup can be seen with git show 20addf8, or git stash list:

    % git stash list
    stash@{0}: lint-staged automatic backup (20addf8)
    

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

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes
  • f0480f0 Thanks @​iiroj! - In the previous version the native git 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.js child_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
  • #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git 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 upgrading git to the latest version.

v15.2.6

Compare Source

Patch Changes
  • #​1433 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

v15.2.4

Compare Source

Patch Changes
  • 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies

v15.2.2

Compare Source

Patch Changes
  • #​1391 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.

v15.2.1

Compare Source

Patch Changes
  • #​1387 e4023f6 Thanks @​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 the stdin of the spawned commands has accepted input, and essentially gotten stuck waiting. Now the stdin is 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

Compare Source

Minor Changes
  • #​1371 f3378be Thanks @​iiroj! - Using the --no-stash flag 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-staged that is automatically enabled when --no-stash is used.
Patch Changes

v15.1.0

Compare Source

Minor Changes
Patch Changes

v15.0.2

Compare Source

Patch Changes
  • #​1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@​7.0.2 to fix an upstream issue affecting lint-staged.

v15.0.1

Compare Source

Patch Changes
  • #​1217 d2e6f8b Thanks @​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

Compare Source

Major Changes
  • #​1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

    This 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

Compare Source

Bug Fixes
  • fix reading config from stdin, introduced in v14.0.0 (#​1317) (fc3bfea)

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • Please upgrade your Node.js version to at least 16.14.0.

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 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

codecov bot commented Jan 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.91%. Comparing base (a94e2b5) to head (7819588).
Report is 89 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #560      +/-   ##
==========================================
+ Coverage   92.38%   92.91%   +0.52%     
==========================================
  Files          26       27       +1     
  Lines        1944     2130     +186     
  Branches      405      448      +43     
==========================================
+ Hits         1796     1979     +183     
- Misses        102      103       +1     
- Partials       46       48       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from db4ab32 to 2bf549d Compare January 3, 2024 16:03
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from beae355 to 75ca5f3 Compare February 5, 2024 16:15
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 5 times, most recently from 03d7341 to 8029cae Compare April 7, 2024 00:24
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from 844d123 to b188ef0 Compare May 14, 2024 17:36
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from f8c9c80 to e67924c Compare May 22, 2024 02:46
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from 002b136 to cbf38f4 Compare May 25, 2024 13:12
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from e21f4b7 to e822f13 Compare June 12, 2024 17:40
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from 320ea44 to 2295883 Compare July 8, 2024 10:32
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from 0eb0737 to 14ef223 Compare August 3, 2024 07:51
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from a77a442 to 5144af4 Compare August 16, 2024 20:50
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 9 times, most recently from 0b7bf80 to e2fd6fa Compare September 2, 2024 08:55
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from c58975a to 429a62e Compare September 8, 2024 20:21
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 6 times, most recently from 2103d97 to b754206 Compare September 17, 2024 09:59
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 9d1bd73 to f0e1421 Compare October 8, 2024 18:18
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from f0e1421 to 8e0c8d5 Compare November 5, 2024 12:33
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 8e0c8d5 to 1605c41 Compare December 10, 2024 15:59
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 1605c41 to 6759034 Compare December 20, 2024 05:52
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from 0565935 to df5e446 Compare December 27, 2024 21:31
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from df5e446 to 7819588 Compare December 28, 2024 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants