bulwark
bulwark copied to clipboard
chore(deps-dev): bump lint-staged from 12.5.0 to 15.2.5
Bumps lint-staged from 12.5.0 to 15.2.5.
Release notes
Sourced from lint-staged's releases.
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]#1368
777d4e9
Thanks@iiroj
! - To improve performance, only uselilconfig
when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.#1373
85eb0dd
Thanks@iiroj
! - When determining git directory, usefs.realpath()
only for symlinks. It looks likefs.realpath()
changes some Windows mapped network filepaths unexpectedly, causing issues.v15.1.0
Minor Changes
- #1344
0423311
Thanks@danielbayley
! - Add support for loading configuration frompackage.yaml
andpackage.yml
files, supported bypnpm
.Patch Changes
... (truncated)
Changelog
Sourced from lint-staged's changelog.
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
- #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]#1368
777d4e9
Thanks@iiroj
! - To improve performance, only uselilconfig
when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.#1373
85eb0dd
Thanks@iiroj
! - When determining git directory, usefs.realpath()
only for symlinks. It looks likefs.realpath()
changes some Windows mapped network filepaths unexpectedly, causing issues.
... (truncated)
Commits
f7e4106
chore(changeset): releasefc75303
build(release): lower next version bump from minor to patch91abea0
fix: improve error logging when failing to parse config file (#1423)31a1f95
build(deps): allow approximately equivalent versions of direct dependenciesee43f15
build(deps): upgrade [email protected]8be6c8e
chore(changeset): release (#1419)4f4537a
build(husky): fix release issue with Husky95d096d
chore(changeset): release (#1411)72483cb
docs: fix typo (#1417)86fba6f
build(deps): update dependencies (#1418)- 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)