⬆️ Updates remark-cli to v12 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
remark-cli (source)	^9.0.0 -> ^12.0.0

---

Release Notes

remarkjs/remark (remark-cli)

v12.0.0

Compare Source

(see 15.0.0)

v11.0.0

Compare Source

(see 15.0.0)

v10.0.1

Compare Source

See remark@14.0.2

v10.0.0

Compare Source

Changelog

• 1b89df5 Update remark-parse, remark-stringify
• aab3c3e Rework list fields
• 3325c33 Add support for label to associations
• 31ef684 Add support for meta in code
• c77d24f Update unified

See also

• remark-cli@6.0.0
• remark-parse@6.0.0
• remark-stringify@6.0.0

Project

• 4f6b3d7 Update logo
• e7f509f Improve npm search ranking of individual packages
• 7d98e30 Fix git.io links
• ce62e7a Refactor code-style

Plugins

• 4c0e28a Add remark-macro to list of plugins
• a4caa67 Add remark-git-contributors to list of plugins
• fe241aa Add remark-outer-toc to list of plugins
• 4fa8b1d Replace deprecated plugin with remark-behead in list of plugins
• 52ffdff Add remark-redact to list of plugins
• 02297a5 Add remark-attr to list of plugins

---

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.

[changelogg]

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

[viezly]

Pull request by bot. No need to analyze

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

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

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
remark-cli	9.0.0...12.0.0	shell	+108/-22	9.77 MB	wooorm

[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