⬆️ Updates conventional-changelog-cli to v4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
conventional-changelog-cli (source)	^2.0.0 -> ^4.0.0

---

Release Notes

conventional-changelog/conventional-changelog (conventional-changelog-cli)

v4.1.0

Compare Source

v4.0.0: standard-changelog: v4.0.0

Compare Source

⚠ BREAKING CHANGES

• Node >= 16 is required
• Now all presets are exports preset config factory function. conventional-changelog-preset-loader now exports new loadPreset and createPresetLoader functions. If you are using presets indirectly, using preset name, no any changes in configuration needed, just upgrade packages to latest versions.

Features

• drop node 14 support (#​1085) (1bce036)
• migrate from chalk to picocolors (#​1074) (c746701)
• unified presets interface (#​1045) (8d0ffbe)

Bug Fixes

• deps: update dependency tempfile to v5 (#​1041) (c026e30)
• fix semver vulnerability (#​1071) (3f5c99d), closes #​1019

v3.0.0: conventional-changelog-cli: v3.0.0

Compare Source

⚠ BREAKING CHANGES

• now all promises are native
• Node >= 14 is required

Code Refactoring

• drop lodash from dependencies where it possible (#​959) (a8b4e12)
• drop q from dependencies (#​974) (d0e5d59)

v2.2.2

Compare Source

2.2.2 (2021-12-24)

Bug Fixes

• docs: update list of available presets (#​871) (2799851)

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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, check this box

---

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

[viezly]

Pull request by bot. No need to analyze

[github-actions]

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

[github-actions]

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

[github-actions]

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
conventional-changelog-cli	2.1.1...4.0.0	None	+45/-50	2.34 MB	oss-bot

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Bin script shell injection	npm	6.14.11	Bin Script: which	@semantic-release/changelog@5.0.1, @semantic-release/commit-analyzer@8.0.1, @semantic-release/git@9.0.0, @semantic-release/github@7.2.0, @semantic-release/npm@7.0.10, @semantic-release/release-notes-generator@9.0.1, semantic-release@17.3.9 via package.json

Next steps

What is bin script shell injection?

This package re-exports a well known shell command via an npm bin script. This is possibly a supply chain attack

Packages should not export bin scripts which conflict with well known shell commands

Take a deeper look at the dependency

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 support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm@6.14.11