chore: bump pulldown-cmark-to-cmark from 14.0.1 to 20.0.0

[dependabot]

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

Release notes

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

v20.0.0

Bug Fixes (BREAKING)

• Add structured error handling for cmark(), cmark_resume() etc When cmark_resume_with_options(), which serves as basis for the other cmark* functions, finds an inconsistent event stream (for example, two consecutive heading start tags), it panics.

  Introduce a custom error type Error in the crate and change the return type of all public functions from fmt::Result<_> to Result<_, Error>.

  The next commit adds an integration test.

Commit Statistics

• 4 commits contributed to the release.
• 4 days passed between releases.
• 1 commit was understood as conventional.
• 1 unique issue was worked on: #91

Commit Details

• #91
  • Revert "fix: harden again manufactured input which could previously trigger assertion failures." (a442910)
• Uncategorized
  • Merge pull request #93 from cip999/resume-error-handling (21f0f5d)
  • Add integration test for CmarkError::UnexpectedEvent (4766cc1)
  • Add structured error handling for cmark(), cmark_resume() etc (fdc5859)

v19.0.1

Bug Fixes

• harden again manufactured input which could previously trigger assertion failures.

Commit Statistics

• 3 commits contributed to the release.
• 19 days passed between releases.
• 1 commit was understood as conventional.
• 1 unique issue was worked on: #91

Commit Details

... (truncated)

Changelog

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

20.0.0 (2024-12-15)

Bug Fixes (BREAKING)

• Add structured error handling for cmark(), cmark_resume() etc When cmark_resume_with_options(), which serves as basis for the other cmark* functions, finds an inconsistent event stream (for example, two consecutive heading start tags), it panics.

  Introduce a custom error type Error in the crate and change the return type of all public functions from fmt::Result<_> to Result<_, Error>.

  The next commit adds an integration test.

Commit Statistics

• 4 commits contributed to the release.
• 4 days passed between releases.
• 1 commit was understood as conventional.
• 1 unique issue was worked on: #91

Commit Details

• #91
  • Revert "fix: harden again manufactured input which could previously trigger assertion failures." (a442910)
• Uncategorized
  • Merge pull request #93 from cip999/resume-error-handling (21f0f5d)
  • Add integration test for CmarkError::UnexpectedEvent (4766cc1)
  • Add structured error handling for cmark(), cmark_resume() etc (fdc5859)

19.0.1 (2024-12-11)

Bug Fixes

• harden again manufactured input which could previously trigger assertion failures.

Commit Statistics

• 4 commits contributed to the release.
• 19 days passed between releases.
• 1 commit was understood as conventional.

... (truncated)

Commits

• 3c850de Release pulldown-cmark-to-cmark v20.0.0
• 21f0f5d Merge pull request #93 from cip999/resume-error-handling
• 4766cc1 Add integration test for CmarkError::UnexpectedEvent
• fdc5859 fix!: Add structured error handling for cmark(), cmark_resume() etc
• a442910 Revert "fix: harden again manufactured input which could previously trigger a...
• aefd5cb Release pulldown-cmark-to-cmark v19.0.1
• c61fdd4 Merge pull request #92 from Byron/fuzz-test
• a368f0f fix: harden again manufactured input which could previously trigger assertion...
• b526d7c refactor tests
• ccc8a52 Release pulldown-cmark-to-cmark v19.0.0
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
pulldown-cmark-to-cmark	[>= 15.0.a, < 15.1]
pulldown-cmark-to-cmark	[>= 16.a, < 17]
pulldown-cmark-to-cmark	[>= 17.a, < 18]
pulldown-cmark-to-cmark	[>= 18.a, < 19]
pulldown-cmark-to-cmark	[>= 19.a, < 20]

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 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.