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 #238

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 20, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 14.0.1 -> 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.


Configuration

📅 Schedule: Branch creation - "before 10am on Saturday" in timezone Asia/Tokyo, 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.

@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from bbd1882 to 91de885 Compare October 27, 2023 18:23
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from 0f1110e to 3fa79ac Compare November 5, 2023 19:40
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from 62b7162 to be96984 Compare November 12, 2023 20:00
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from f7d62a1 to ea275cc Compare November 24, 2023 18:14
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from 1690d23 to 646f838 Compare December 2, 2023 00:03
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from cce24dd to 871483a Compare December 3, 2023 19:20
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from a3f09f1 to 513d1d2 Compare December 17, 2023 18:15
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from dcea3d9 to dd327dd Compare December 24, 2023 19:01
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from 9ccd853 to 53a9a68 Compare January 5, 2024 18:19
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 01ff71f to 7f5379a Compare January 12, 2024 23:17
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 7f5379a to 5dc732d Compare January 14, 2024 19:58
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from d14e809 to f86e9e0 Compare September 6, 2024 19:52
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from f86e9e0 to d805af0 Compare September 8, 2024 18:01
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from ca24c28 to bd481ff Compare September 20, 2024 19:57
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from daf84f7 to b0c1da5 Compare September 29, 2024 19:33
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from bb229b4 to 1c21e29 Compare October 6, 2024 19:39
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 17591c5 to 797ce61 Compare October 18, 2024 21:06
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 5981fce to 2b90884 Compare October 27, 2024 18:27
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 2b90884 to f357d9c Compare November 3, 2024 19:02
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 327d4d6 to b1525ab Compare November 17, 2024 18:36
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 6b81659 to d15bdcb Compare November 29, 2024 19:58
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 3 times, most recently from d4871bf to ea93344 Compare December 10, 2024 14:22
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 4b08763 to cf74fd0 Compare December 20, 2024 23:37
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from eafcb06 to 618ec6d Compare December 28, 2024 13:46
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 618ec6d to 28ac743 Compare December 29, 2024 18:58
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 28ac743 to ea52f81 Compare January 5, 2025 20:09
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