build(deps-dev): bump lint-staged from 10.5.4 to 13.0.3 in /ui

[dependabot]

Bumps lint-staged from 10.5.4 to 13.0.3.

Release notes

Sourced from lint-staged's releases.

v13.0.3

13.0.3 (2022-06-24)

Bug Fixes

• correctly handle git stash when using MSYS2 (#1178) (0d627a5)

v13.0.2

13.0.2 (2022-06-16)

Bug Fixes

• use new --diff and --diff-filter options when checking task modifications (1a5a66a)

v13.0.1

13.0.1 (2022-06-08)

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 of setInterval for killing tasks on failure (c508b46)

v13.0.0

13.0.0 (2022-06-01)

Bug Fixes

• deps: update execa@^6.1.0 (659c85c)
• deps: update yaml@^2.1.1 (2750a3d)

Features

• remove support for Node.js 12 (5fb6df9)

BREAKING CHANGES

... (truncated)

Commits

• 0d627a5 fix: correctly handle git stash when using MSYS2 (#1178)
• 1a5a66a fix: use new --diff and --diff-filter options when checking task modifica...
• 32806da test: split integration tests into separate files and improve isolation
• 4384114 refactor: reuse Listr stuff better
• f27f1d4 fix: correct spelling of "0 files"
• f2c6bdd fix: suppress error from process.kill when killing tasks on failure
• c5cec0a docs: add section about task concurrency to README.md
• 5bf1f18 docs: remove mrm from README.md
• c508b46 perf: use EventsEmitter instead of setInterval for killing tasks on failure
• 1a77e42 fix(deps): update pidtree@^0.6.0 to fix screen size error in WSL
• 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 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)

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

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.

[secure-code-warrior-for-github]

Micro-Learning Topic: Race condition (Detected by phrase)

Matched on "race condition"

What is this? (2min video)

A race condition is a flaw that produces an unexpected result when the timing of actions impact other actions.

Try this challenge in Secure Code Warrior

[dependabot]

Superseded by #418.