objection-hashid
objection-hashid copied to clipboard
Update dependency lint-staged to v13
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
lint-staged | ^12.3.8 -> ^13.0.0 |
Release Notes
okonet/lint-staged
v13.0.3
Bug Fixes
v13.0.2
Bug Fixes
- use new
--diff
and--diff-filter
options when checking task modifications (1a5a66a)
v13.0.1
Bug Fixes
- correct spelling of "0 files" (f27f1d4)
- suppress error from
process.kill
when killing tasks on failure (f2c6bdd) - deps: update pidtree@^0.6.0 to fix screen size error in WSL (1a77e42)
- ignore "No matching pid found" error (cb8a432)
- prevent possible race condition when killing tasks on failure (bc92aff)
Performance Improvements
- use
EventsEmitter
instead ofsetInterval
for killing tasks on failure (c508b46)
v13.0.0
Bug Fixes
Features
- remove support for Node.js 12 (5fb6df9)
BREAKING CHANGES
-
lint-staged
will no longer support Node.js 12, which is EOL since 30 April 2022
v12.5.0
Bug Fixes
- include all files when using
--config <path>
(641d1c2) - skip backup stash when using the
--diff
option (d4da24d)
Features
- add
--diff-filter
option for overriding list of (staged) files (753ef72) - add
--diff
option for overriding list of (staged) files (35fcce9)
v12.4.3
Bug Fixes
- deps: downgrade [email protected] to support Node.js 12 (383a96e)
- deps: update commander@^9.2.0 (22ebf52)
- deps: update yaml@^2.0.1 (ec73af0)
v12.4.2
Bug Fixes
- correctly handle --max-arg-length cli option (1db5f26)
v12.4.1
Bug Fixes
- correctly handle symlinked config files (b3f63ec)
v12.4.0
Bug Fixes
- handle empty input by returning empty array from
parseGitZOutput
(a118817) - limit configuration discovery to cwd (d8fdf1d)
- restore functionality of parent globs for a single configuration file (877ab4c)
Features
- expose
--max-arg-length
cli option (e8291b0)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/objection
npm ERR! dev objection@"^3.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer objection@">= 2 < 3" from [email protected]
npm ERR! node_modules/objection-visibility
npm ERR! dev objection-visibility@"^1.0.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/objection
npm ERR! peer objection@">= 2 < 3" from [email protected]
npm ERR! node_modules/objection-visibility
npm ERR! dev objection-visibility@"^1.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-20T18_59_58_296Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-20T18_59_58_296Z-debug-0.log