fix(deps): update dependency marked to v13

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
marked (source)	`^12.0.0` -> `^13.0.0`

Release Notes

markedjs/marked (marked)

### [`v13.0.0`](https://togithub.com/markedjs/marked/releases/tag/v13.0.0) [Compare Source](https://togithub.com/markedjs/marked/compare/v12.0.2...v13.0.0) ##### Bug Fixes - Fix blockquote code continuation ([#3264](https://togithub.com/markedjs/marked/issues/3264)) ([7ab8185](https://togithub.com/markedjs/marked/commit/7ab818502ed537ab8eed22dc9cf4f7602232aa53)) - Add parser as a property on the Renderer object ([#3291](https://togithub.com/markedjs/marked/issues/3291)) - Send block text tokens to the text renderer ([#3291](https://togithub.com/markedjs/marked/issues/3291)) ##### Features - Send token objects to renderers ([#3291](https://togithub.com/markedjs/marked/issues/3291)) ([1ce59ea](https://togithub.com/markedjs/marked/commit/1ce59ea827272b5d067f1e06d3ee4a1d52b1d9bb)) - Add space renderer that returns empty string by default ([#3291](https://togithub.com/markedjs/marked/issues/3291)) - Add header and align properties to TableCell token ([#3291](https://togithub.com/markedjs/marked/issues/3291)) - Add TableRow token ([#3291](https://togithub.com/markedjs/marked/issues/3291)) - Add Checkbox token ([#3291](https://togithub.com/markedjs/marked/issues/3291)) ##### BREAKING CHANGES - Add space token after blockquote and hr if there are multiple newlines - Send token objects to renderers and move logic to parse tokens from the parser to the renderers. - Most extensions that update marked renderers should still work with this version but will break in a future major version. - Extensions that change marked renderers will need to be updated and use new option `useNewRenderer` and accept a token object instead of multiple parameters. See updated [Renderer docs](https://marked.js.org/using_pro#renderer) ```js // v12 renderer extension const extension = { renderer: { heading(text, level) { // increase level by 1 return `${text}`; } } }; marked.use(extension); ``` ```js // v13 renderer extension const extension = { useNewRenderer: true, renderer: { heading(token) { // increase depth by 1 const text = this.parser.parseInline(token.tokens); const level = token.depth; return `${text}`; } } }; marked.use(extension); ```

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: marked-terminal@7.0.0
npm error Found: marked@13.0.0
npm error node_modules/marked
npm error   marked@"^13.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer marked@">=1 <13" from marked-terminal@7.0.0
npm error node_modules/marked-terminal
npm error   marked-terminal@"^7.0.0" from the root project
npm error   marked-terminal@"^7.0.0" from semantic-release@23.0.8
npm error   node_modules/semantic-release
npm error     dev semantic-release@"23.0.8" from the root project
npm error     7 more (@semantic-release/changelog, ...)
npm error
npm error Conflicting peer dependency: marked@12.0.2
npm error node_modules/marked
npm error   peer marked@">=1 <13" from marked-terminal@7.0.0
npm error   node_modules/marked-terminal
npm error     marked-terminal@"^7.0.0" from the root project
npm error     marked-terminal@"^7.0.0" from semantic-release@23.0.8
npm error     node_modules/semantic-release
npm error       dev semantic-release@"23.0.8" from the root project
npm error       7 more (@semantic-release/changelog, ...)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-15T09_14_18_902Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-15T09_14_18_902Z-debug-0.log

StinkyBenji / semantic-release-image