chore(deps): update dependency lint-staged to v10

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
lint-staged	devDependencies	major	9.5.0 -> 10.0.7

---

Release Notes

okonet/lint-staged

v10.0.7

Compare Source

Bug Fixes

• replace fs.promises with util.promisify (#​786) (f71c1c9)

v10.0.6

Compare Source

Bug Fixes

• make sure deleted files aren't restored due to git bugs (#​778) (6bfbe6c)

v10.0.5

Compare Source

Bug Fixes

• always resolve real git config dir location if .git is a file (#​784) (b98a5ed)

v10.0.4

Compare Source

Bug Fixes

• use verbose renderer when TERM=dumb (#​782) (9c08e8e)

v10.0.3

Compare Source

Bug Fixes

• correctly restore untracked files after running (#​780) (4010db0)

v10.0.2

Compare Source

Bug Fixes

• only warn about git add when it's the exact command (24febb3)
• parse command string with string-argv unless --shell is used (4cb4dde)
• print a better warning when the initial commit is missing (293547d)

v10.0.1

Compare Source

Bug Fixes

• preserve merge states in submodules (#​769) (e646b2c)

v10.0.0

Compare Source

Bug Fixes

• add all modified files to git index with git add . (bf532c2)
• automatically add modifications only to originally staged files (083b8e7)
• better workaround for git stash --keep-index bug (f3ae378)
• correctly leave only staged files for running tasks (cfde9ca)
• correctly recover when unstaged changes cannot be restored (d091f71)
• correctly restore untracked files from backup stash (c7d0592)
• error handling skips dropping backup stash after internal git errors (30b4809)
• fail with a message when backup stash is missing (1b64239)
• gitWorkflow handles active merge mode (2f1e886)
• handle git MERGE_* files separately; improve error handling (da22cf2)
• improve debug logging (f88e226)
• keep untracked files around by backing them up (fc03fdc)
• max arg length is by default half of the allowed to prevent edge cases (80406c2)
• prevent Listr from hiding git add warning (cce9809)
• restore metadata about git merge before running tasks (f8ddfc2)
• retry failing apply with 3-way merge (76cb08f)
• support binary files (7b3a334)
• try applying unstaged changes before handling errors (357934f)
• update warning about git add, and to README (6467a66)
• workaround for stashing deleted files for git < 2.23 (1a87333)

Features

• automatically stage task modifications (74ed28d)
• bump Node.js version dependency to at least 10.13.0 (#​747) (814b9df)
• split tasks into chunks to support shells with limited max argument length (#​732) (cb43872)
• support async function tasks (20d5c5d)
• throw error to prevent empty commits unless --allow-empty is used (#​762) (8bdeec0)
• use git stashes for gitWorkflow (40a5db1)
• warn when task contains "git add" (5208399)

BREAKING CHANGES

• Previously, lint-staged would allow empty commits in the situation where a linter task like "prettier --write" reverts all staged changes automatically. Now the default behaviour is to throw an error with a helpful warning message. The --allow empty option can be used to allow empty commits, or allowEmpty: true for the Node.js API.
• Node.js v8 is no longer supported because it will reach EOL on 2019-12-31
• Prior to version 10, tasks had to manually include git add as the final step. This behavior has been integrated into lint-staged itself in order to prevent race conditions with multiple tasks editing the same files. If lint-staged detects git add in task configurations, it will show a warning in the console. Please remove git add from your configuration after upgrading.

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you tick the rebase/retry checkbox below.

🔕 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 WhiteSource Renovate. View repository job log here.

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	92	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	91	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	90	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	91	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	88	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	91	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	91	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0

[lighthousebot]

Updated Lighthouse report for the changes in this PR:

Category	New score	Required threshold
Performance	88	80
Accessibility	100	80
Best Practices	93	80
SEO	90	80
Progressive Web App	73	80

Tested with Lighthouse version: 4.1.0