build(deps-dev): bump lint-staged from 13.3.0 to 15.1.0

[dependabot]

Bumps lint-staged from 13.3.0 to 15.1.0.

Release notes

Sourced from lint-staged's releases.

v15.1.0

Minor Changes

• #1344 0423311 Thanks @​danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

• #1355 105d901 Thanks @​iiroj! - Suppress some warnings when using the "--quiet" flag

v15.0.2

Patch Changes

• #1339 8e82364 Thanks @​iiroj! - Update dependencies, including [email protected] to fix an upstream issue affecting lint-staged.

v15.0.1

Patch Changes

• #1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

v15.0.0

Major Changes

• #1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

  This release drops support for Node.js 16, which is EOL after 2023-09-11. Please upgrade your Node.js to the latest version.

  Additionally, all dependencies have been updated to their latest versions.

v14.0.1

14.0.1 (2023-08-21)

Bug Fixes

• fix reading config from stdin, introduced in v14.0.0 (#1317) (fc3bfea)

v14.0.0

14.0.0 (2023-08-13)

Features

• drop support for Node.js 14 (#1312) (9da8777)

BREAKING CHANGES

• Please upgrade your Node.js version to at least 16.14.0.

Changelog

Sourced from lint-staged's changelog.

15.1.0

Minor Changes

• #1344 0423311 Thanks @​danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

• #1355 105d901 Thanks @​iiroj! - Suppress some warnings when using the "--quiet" flag

15.0.2

Patch Changes

• #1339 8e82364 Thanks @​iiroj! - Update dependencies, including [email protected] to fix an upstream issue affecting lint-staged.

15.0.1

Patch Changes

• #1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

15.0.0

Major Changes

• #1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

  This release drops support for Node.js 16, which is EOL after 2023-09-11. Please upgrade your Node.js to the latest version.

  Additionally, all dependencies have been updated to their latest versions.

v14.0.1 - 21 Aug 2023

Bug Fixes

• fix reading config from stdin, introduced in v14.0.0 (#1317) (fc3bfea)

v14.0.0 - 13 Aug 2023

Features

• drop support for Node.js 14 (#1312) (9da8777)

BREAKING CHANGES

• Please upgrade your Node.js version to at least 16.14.0.

Commits

• 26eee9d chore(changeset): release
• fed0770 docs: update README to mention v13.3.0
• 70487af test: add unit test for uncovered error
• 0423311 docs: add changeset
• 19fe984 refactor: declare some variables
• 0ac8e91 feat: add support for package.yaml
• e023c2a test: add integration test for symbolic link git dir
• 4b9fb10 chore(deps): update dependencies
• 105d901 fix: suppress warnings when using --quiet
• 21aeeb5 chore(deps): update dependencies
• 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)

[pull-checklist]

Global Compliance

• Have you written your compliance handover

[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 detected.
• 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.

[dependabot]

Superseded by #58.