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.2.10 #13

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 15.2.5 -> 15.2.10 age adoption passing confidence

Release Notes

lint-staged/lint-staged (lint-staged)

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.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 from 4358e1f to 5f5a011 Compare June 12, 2024 20:11
@renovate 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 renovate bot force-pushed the renovate/lint-staged-15.x branch from 5f5a011 to 421f089 Compare August 3, 2024 08:02
@renovate 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 renovate bot force-pushed the renovate/lint-staged-15.x branch from 421f089 to 1df6d73 Compare August 13, 2024 06:52
@renovate 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 renovate bot force-pushed the renovate/lint-staged-15.x branch from 1df6d73 to 9fc1e7b Compare September 1, 2024 15:32
@renovate 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants