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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lint-staged	11.2.3 -> 12.1.2

---

Release Notes

okonet/lint-staged

v12.1.2

Compare Source

Bug Fixes

• fix Windows JS config loading by using file:// URLs (f20ddf9)
• fix YAML config loading (0082ec2)
• improve error logging in loadConfig (e7b6412)

v12.1.1

Compare Source

Bug Fixes

• await for dynamic import promise when loading JS config (e96b6d9)

v12.1.0

Compare Source

Features

• allow loading .js config file with ESM syntax (410c3ba)
• replace cosmiconfig with lilconfig + yaml to reduce dependencies (e7f9fa0)
• support loading .mjs config (8d3b176)

v12.0.3

Compare Source

Bug Fixes

• install enquirer (e01585f)

v12.0.2

Compare Source

Bug Fixes

• remove npm version requirement (#​1047) (e50d6d4)

v12.0.1

Compare Source

Bug Fixes

• read version number from lint-staged package.json instead of package.json in cwd (#​1043) (#​1044) (9f9213d)

v12.0.0

Compare Source

Features

• convert to native ESM module (#​1038) (7240f61)

BREAKING CHANGES

• lint-staged is now a pure ESM module, and thus
  requires Node.js version ^12.20.0 || ^14.13.1 || >=16.0.0.

To update your Node.js integration, please use:

// const lintStaged = require('lint-staged')
import lintStaged from 'lint-staged'

v11.2.6

Compare Source

Bug Fixes

• revert back to cosmiconfig from lilconfig (#​1035) (e035b80), closes #​1033 #​981

v11.2.5

Compare Source

Bug Fixes

• correctly import js-yaml to fix yaml config loading (#​1033) (612d806)

v11.2.4

Compare Source

Performance Improvements

• replace cosmiconfig with lilconfig (#​981) (04529e2)

---

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 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, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[pull-request-quantifier-deprecated]

This PR has 143 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Medium
Size       : +92 -51
Percentile : 48.6%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.yaml : +91 -50

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.