search

kubevirt / kubevirt.github.io

KubeVirt website repo, documentation at https://kubevirt.io/user-guide/
https://kubevirt.io
MIT License
29 stars 109 forks source link

Bump markdown-it and yaspeller #882

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps markdown-it to 12.3.2 and updates ancestor dependency yaspeller. These dependencies need to be updated together.

Updates markdown-it from 10.0.0 to 12.3.2

Changelog

Sourced from markdown-it's changelog.

[12.3.2] - 2022-01-08

Security

[12.3.1] - 2022-01-07

Fixed

  • Fix corner case when tab prevents paragraph continuation in lists, #830.

[12.3.0] - 2021-12-09

Changed

  • StateInline.delimiters[].jump is removed.

Fixed

  • Fixed quadratic complexity in pathological ***<10k stars>***a***<10k stars>*** case.

[12.2.0] - 2021-08-02

Added

  • Ordered lists: add order value to token info.

Fixed

  • Always suffix indented code block with a newline, #799.

[12.1.0] - 2021-07-01

Changed

  • Updated CM spec compatibility to 0.30.

[12.0.6] - 2021-04-16

Fixed

  • Newline in alt should be rendered, #775.

[12.0.5] - 2021-04-15

Fixed

  • HTML block tags with === inside are no longer incorrectly interpreted as headers, #772.
  • Fix table/list parsing ambiguity, #767.

[12.0.4] - 2020-12-20

Fixed

  • Fix crash introduced in 12.0.3 when processing strikethrough (~~) and similar plugins, #742.
  • Avoid fenced token mutation, #745.

[12.0.3] - 2020-12-07

Fixed

... (truncated)

Commits


Updates yaspeller from 7.0.0 to 7.2.1

Release notes

Sourced from yaspeller's releases.

v7.2.1

--ignore-tags Not work properly in Markdown files with HTML #176

v7.2.0

  • Update deps in package.json
  • Fixed sitemap bug #169

v7.1.0

Added junit report #171 @​Lootjs.

Changelog

Sourced from yaspeller's changelog.

v7.2.1

  • --ignore-tags Not work properly in Markdown files with HTML #176

v7.2.0

  • Update deps in package.json
  • Fixed sitemap bug #169

v7.1.0

Added junit report #171 @​Lootjs.

Commits


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 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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/kubevirt/kubevirt.github.io/network/alerts).
kubevirt-bot commented 1 year ago

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
jobbler commented 1 year ago

This appears to be the same PR as #880. Am I missing something here? Should this be closed as a duplicate?

cwilkers commented 1 year ago

I just approved #880 so we can check if this triggers a merge conflict on rebase.

cwilkers commented 1 year ago

/ok-to-test

cwilkers commented 1 year ago

/approve /lgtm

kubevirt-bot commented 1 year ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cwilkers

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/kubevirt/kubevirt.github.io/blob/main/OWNERS)~~ [cwilkers] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment