npm: bump @commitlint/cli from 16.3.0 to 20.0.0

[dependabot]

Bumps @commitlint/cli from 16.3.0 to 20.0.0.

Release notes

Sourced from @​commitlint/cli's releases.

v20.0.0

20.0.0 (2025-09-25)

Features

• feat(rules)!: make body-max-line-length ignore lines with URLs (#4486) (2f37a88), closes #4486 by @​aspiers

BREAKING CHANGES

• when lines contain URLs exceeding the maximum line length body-max-line-length will be ignored

Full Changelog: conventional-changelog/commitlint@v19.9.1...v20.0.0

v19.9.1

19.9.1 (2025-08-29)

Bug Fixes

• fix: add TypeScript support and configuration for pnpm scopes by @​alsmadi99 in conventional-changelog/commitlint#4544

Full Changelog: conventional-changelog/commitlint@v19.9.0...v19.9.1

v19.9.0

19.9.0 (2025-08-26)

Features

• bug(config-pnpm-scopes): migrate package to TypeScript by @​alsmadi99 in conventional-changelog/commitlint#4541 (type got messed up)

Chore, docs, etc.

• docs: add a note about configuration under node24 by @​sodle in conventional-changelog/commitlint#4406
• chore: add Ubuntu 24.04 and Windows 2025 to CI by @​Marukome0743 in conventional-changelog/commitlint#4435
• docs: refactor CI setup example of GitHub Actions by @​Marukome0743 in conventional-changelog/commitlint#4439
• ci: use tags for immutable github actions by @​Fdawgs in conventional-changelog/commitlint#4458
• chore: migrate eslint-plugin-import to eslint-plugin-import-x by @​JounQin in conventional-changelog/commitlint#4473
• ci: add commitlint GitHub Actions by @​Marukome0743 in conventional-changelog/commitlint#4440

... (truncated)

Changelog

Sourced from @​commitlint/cli's changelog.

20.0.0 (2025-09-25)

Note: Version bump only for package @​commitlint/cli

19.8.1 (2025-05-08)

Bug Fixes

• update dependency tinyexec to v1 (#4332) (e49449f)

19.8.0 (2025-03-07)

Performance Improvements

• use node: prefix to bypass require.cache call for builtins (#4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @​commitlint/cli

19.6.1 (2024-12-15)

Note: Version bump only for package @​commitlint/cli

19.6.0 (2024-11-19)

Note: Version bump only for package @​commitlint/cli

... (truncated)

Commits

• 407be6c v20.0.0
• 3c30200 v19.8.1
• e49449f fix: update dependency tinyexec to v1 (#4332)
• e2e3b67 Chore/deps prettier v3 3 (#4320)
• b92f072 chore: update gitHead after failed publish (#4315)
• e82f05a v19.8.0
• e685618 chore: add missing 'use strict' directives (#4301)
• 0cd8f41 perf: use node: prefix to bypass require.cache call for builtins (#4302)
• b0e851c v19.7.1
• e2dc109 v19.6.1
• 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)

[dependabot]

Labels

The following labels could not be found: npm. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	chart-csv@​1.0.3
	deploy-to-gh-pages@​1.3.7
	@​changesets/​changelog-github@​0.4.8
	changelog-machine@​1.1.0
	@​commitlint/​cli@​20.0.0
	csvnorm@​1.1.0
	@​cadolabs/​crowdin-cli@​3.0.21
	danger-plugin-spellcheck@​2.1.0
	@​bitjson/​npm-scripts-info@​1.0.0
	adr-tools@​2.0.4
	check-for-leaks@​1.2.1
	dockerfile_lint@​0.3.4
	alex@​9.1.1
	cost-of-modules@​1.0.1
	browser-sync@​2.29.3
	@​changesets/​write@​0.2.3
	all-contributors-cli@​6.26.1
	conventional-changelog-cli@​2.2.2
	@​commitlint/​config-conventional@​16.2.4
	@​changesets/​cli@​2.29.7
	chromatic@​6.24.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: >= 0 Patched version: No patched versions From: ? → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12 From: ? → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12 From: ? → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[dependabot]

Superseded by #3498.