build(deps-dev): bump commitlint from 17.8.1 to 18.4.2

[dependabot]

Bumps commitlint from 17.8.1 to 18.4.2.

Release notes

Sourced from commitlint's releases.

v18.4.2

18.4.2 (2023-11-16)

Bug Fixes

• Fix/3768: Consider ESM when selecting cosmiconfig loaders by @​joberstein in conventional-changelog/commitlint#3776

Full Changelog: conventional-changelog/commitlint@v18.4.1...v18.4.2

v18.4.1

18.4.1 (2023-11-12)

Bug Fixes

• update cosmiconfig to specific version by @​joberstein (#3755) (636b8b1)

Full Changelog: conventional-changelog/commitlint@v18.4.0...v18.4.1

v18.4.0

18.4.0 (2023-11-10)

Features

• bump cosmiconfig version and conditionally support mjs config by @​joberstein (#3747) (a2b65fc)

New Contributors

• @​gabrielecanepa made their first contribution in conventional-changelog/commitlint#3737

Full Changelog: conventional-changelog/commitlint@v18.3.0...v18.4.0

v18.3.0

18.3.0 (2023-10-26)

Bug Fixes

• update dependency @​types/node to v18.18.7 (#3726) (dcc0424)

Features

... (truncated)

Changelog

Sourced from commitlint's changelog.

18.4.2 (2023-11-16)

Note: Version bump only for package commitlint

18.4.1 (2023-11-12)

Note: Version bump only for package commitlint

18.4.0 (2023-11-10)

Note: Version bump only for package commitlint

18.2.0 (2023-10-26)

Note: Version bump only for package commitlint

18.1.0 (2023-10-25)

Note: Version bump only for package commitlint

18.0.0 (2023-10-20)

• chore!: minimum node version v18 (#3644) (5b4aeaf), closes #3644

BREAKING CHANGES

• drop node v14 and v16 support

... (truncated)

Commits

• 0370a85 v18.4.2
• 74b2f82 v18.4.1
• 0546cd7 v18.4.0
• 9b80b6e v18.2.0
• ab46d53 v18.1.0
• 3cb6647 v18.0.0
• 5b4aeaf chore!: minimum node version v18 (#3644)
• See full diff 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-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 #54.