build(deps-dev): bump lint-staged from 13.1.2 to 15.2.7
Bumps lint-staged from 13.1.2 to 15.2.7.
Release notes
Sourced from lint-staged's releases.
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
- #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]
... (truncated)
Changelog
Sourced from lint-staged's changelog.
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
Patch Changes
15.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.15.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.15.2.0
Minor Changes
... (truncated)
Commits
87e4b30chore(changeset): release (#1441)a39e829docs: adjust changeseta51be80fix: drop option to support earlier Git versionsa91d942chore(changeset): release119adb2fix: use native git command to get .git directorye0386dcfix: use native git command to get top-level directory for repo6593870ci: test Node.js versions against current instead of latest dependency6c226c5ci: add workflow for testing required Node.js semver rangef7e4106chore(changeset): releasefc75303build(release): lower next version bump from minor to patch- 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)
Deployment failed with the following error:
Environment Variable "GITHUB_CLIENT_ID" references Secret "github-client-id", which does not exist.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.