carbon-components-vue
carbon-components-vue copied to clipboard
chore(deps-dev): bump lint-staged from 12.5.0 to 15.2.10
Bumps lint-staged from 12.5.0 to 15.2.10.
Release notes
Sourced from lint-staged's releases.
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.3
Patch Changes
v15.2.2
Patch Changes
... (truncated)
Changelog
Sourced from lint-staged's changelog.
15.2.10
Patch Changes
15.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.15.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.
15.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.15.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.15.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]15.2.4
Patch Changes
15.2.3
... (truncated)
Commits
163112fchore(changeset): release829575cMerge pull request #1471 from lint-staged/updates893ca84refactor: remove unused parameter defaulta661f46build(deps): migrate to ESLint 9e3f283bbuild(deps): update minor dependencies35483b9docs: add some more concrete command examples to the README0ce5e14chore(changeset): release (#1465)b69ce2dfix: set max event listeners to the number of tasks (#1463)52f6eefchore(changeset): release (#1462)8d8fe23build: update repository url in package.json- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)