⬆️ Bump pulldown-cmark-to-cmark from 14.0.1 to 21.1.0

[dependabot]

Bumps pulldown-cmark-to-cmark from 14.0.1 to 21.1.0.

Release notes

Sourced from pulldown-cmark-to-cmark's releases.

v21.1.0

New Features

• Improve CommonMark conformance testing output This is a major improvement to the rendering of the failing CommonMark conformance test output, that should make it easier to read and understand when pulldown-cmark-to-cmark is producing erroneous output.

  Additionally, this introduces a way to force the printing of the CommonMark failure report from the command line:

  $ FULL_CMARK_RESULTS=true cargo test
  

  and documents in CONTRIBUTING.md that new contributors may want to start with trying to improve conformance.

  This removes #[should_panic] from the main CommonMark test. Instead, we now hard-code in how many of the CommonMark tests are known to pass.

  If the number that actually passes increases or decreases, this test will fail, informing the user either that they have introduced a bug (decrease), or that they've successfully improved conformance (increase).

  Previously, if a change accidentally reduce the conformance, there was no easy way to know, since that information was not stored/tracked in any way.

Other

• Drop comment headers

Refactor

• Add Repeated utility to simplify writing repeated content

• Move and group related code My impression reading through the code in this project is that top-level statements have gotten a bit intertangled over time; this tries to reorder things to have a clearer flow and structure, grouping related things together.

  For example, this moves the recently added Error enum up above all of the API functions, instead of leaving it somewhat arbitrarily nestled between cmark_resume_with_options() and cmark_resume_one_event().

  No code changes were made to the body of functions or types. This also does not change any of the public APIs, only where code is located.

... (truncated)

Changelog

Sourced from pulldown-cmark-to-cmark's changelog.

21.1.0 (2025-11-09)

New Features

• Improve CommonMark conformance testing output This is a major improvement to the rendering of the failing CommonMark conformance test output, that should make it easier to read and understand when pulldown-cmark-to-cmark is producing erroneous output.

  Additionally, this introduces a way to force the printing of the CommonMark failure report from the command line:

  $ FULL_CMARK_RESULTS=true cargo test
  

  and documents in CONTRIBUTING.md that new contributors may want to start with trying to improve conformance.

  This removes #[should_panic] from the main CommonMark test. Instead, we now hard-code in how many of the CommonMark tests are known to pass.

  If the number that actually passes increases or decreases, this test will fail, informing the user either that they have introduced a bug (decrease), or that they've successfully improved conformance (increase).

  Previously, if a change accidentally reduce the conformance, there was no easy way to know, since that information was not stored/tracked in any way.

Other

• Drop comment headers

Refactor

• Add Repeated utility to simplify writing repeated content

• Move and group related code My impression reading through the code in this project is that top-level statements have gotten a bit intertangled over time; this tries to reorder things to have a clearer flow and structure, grouping related things together.

  For example, this moves the recently added Error enum up above all of the API functions, instead of leaving it somewhat arbitrarily nestled between cmark_resume_with_options() and cmark_resume_one_event().

  No code changes were made to the body of functions or types. This also does not change any of the public APIs, only where code is located.

... (truncated)

Commits

• 4fa1f9e Release pulldown-cmark-to-cmark v21.1.0
• d69f748 Release pulldown-cmark-to-cmark v21.0.0
• bf34a3c Merge pull request #104 from ConnorGray/connorgray/refactor-5
• 942c42b refactor: Add Repeated utility to simplify writing repeated content
• 3005f1b Merge pull request #103 from ConnorGray/connorgray/refactor-4
• 5b93e7e review: Drop comment headers
• 30b706b refactor: Move and group related code
• 3169307 Merge pull request #102 from ConnorGray/connorgray/revamp-conformance-testing
• ac3aaec Merge pull request #101 from ConnorGray/connorgray/refactor-3
• 29c8c20 Merge pull request #100 from ConnorGray/connorgray/refactor-2
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.