v2fly-github-io
v2fly-github-io copied to clipboard
Chore: bump lint-staged from 13.2.2 to 15.2.7
Bumps lint-staged from 13.2.2 to 15.2.7.
Release notes
Sourced from lint-staged's releases.
v15.2.7
Patch Changes
- #1440
a51be80
Thanks@iiroj
! - In the previous version the nativegit 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 upgradinggit
to the latest version.v15.2.6
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
Patch Changes
#1424
31a1f95
Thanks@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
91abea0
Thanks@iiroj
! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15
Thanks@iiroj
! - Upgrade [email protected]v15.2.4
Patch Changes
v15.2.3
Patch Changes
v15.2.2
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
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 thestdin
of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin
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
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
#1362
17bc480
Thanks@antonk52
! - update [email protected]
... (truncated)
Changelog
Sourced from lint-staged's changelog.
15.2.7
Patch Changes
- #1440
a51be80
Thanks@iiroj
! - In the previous version the nativegit 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 upgradinggit
to the latest version.15.2.6
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.15.2.5
Patch Changes
#1424
31a1f95
Thanks@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
91abea0
Thanks@iiroj
! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15
Thanks@iiroj
! - Upgrade [email protected]15.2.4
Patch Changes
15.2.3
Patch Changes
15.2.2
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.15.2.1
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 thestdin
of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin
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.15.2.0
Minor Changes
... (truncated)
Commits
87e4b30
chore(changeset): release (#1441)a39e829
docs: adjust changeseta51be80
fix: drop option to support earlier Git versionsa91d942
chore(changeset): release119adb2
fix: use native git command to get .git directorye0386dc
fix: use native git command to get top-level directory for repo6593870
ci: test Node.js versions against current instead of latest dependency6c226c5
ci: add workflow for testing required Node.js semver rangef7e4106
chore(changeset): releasefc75303
build(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 rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)