Bump mistune from 3.3.0 to 3.3.3

[dependabot]

Bumps mistune from 3.3.0 to 3.3.3.

Release notes

Sourced from mistune's releases.

v3.3.3

   🐞 Bug Fixes

• Set prev token in render_list_item and add block_text to ignore_blocks  -  by @​gaoflow in lepture/mistune#456 (0799e)
• Improve nested bracket link input  -  by @​lepture (fe02f)
• Escape literal emphasis markers in MarkdownRenderer  -  by @​Sanjays2402 (b0429)
• Use SAFE_PROTOCOLS instead of HARMFUL_PROTOCOLS  -  by @​lepture (4009f)
• Add max_emphasis_depth  -  by @​lepture (0938f)
• Add image max depth  -  by @​lepture (cca5e)
• inline: Use original run length in emphasis multiple-of-3 rule  -  by @​greymoth-jp and Claude Opus 4.8 (1M context) (2d26b)

   🏎 Performance

• Improve link label parsing performance  -  by @​lepture (e001d)
• Improve performance for math and formatting plugins  -  by @​lepture (c2228)
• Improve for footnotes, ruby and spoiler  -  by @​lepture (ae7e9)

    View changes on GitHub

v3.3.2

   🐞 Bug Fixes

• Try to support python 3.8  -  by @​lepture (c9f1a)
• Resolve mypy issues for python 3.8 and 3.9+  -  by @​lepture (29b70)

    View changes on GitHub

v3.3.1

   🐞 Bug Fixes

• abbr: Update process_text method in abrr, adding parse_emphasis parameter  -  by @​lepture (ae850)
• directive: Use correct file path for include directive  -  by @​lepture (18c21)

    View changes on GitHub

Changelog

Sourced from mistune's changelog.

Version 3.3.3

Released on Jul 9, 2026

• Limit deeply nested emphasis and image parsing to avoid RecursionError.
• Fix repeated link suffix and unclosed formatting marker performance issues.
• Fix unclosed inline spoiler performance issues.
• Avoid recursive parsing for adjacent ruby tokens.
• Speed up footnote reference indexing.

Version 3.3.2

Released on Jun 23, 2026

• Fix Python 3.8 import compatibility in the inline parser.
• Fix mypy compatibility for list parsing on Python 3.8 and 3.9+.

Version 3.3.1

Released on Jun 22, 2026

• Fix abbr plugin compatibility with escaped inline text.
• Normalize included Markdown line endings before parsing directives.

Commits

• 060f73a chore: release 3.3.3
• ae7e9d5 perf: improve for footnotes, ruby and spoiler
• c2228a2 perf: improve performance for math and formatting plugins
• e001d51 perf: improve link label parsing performance
• cca5ee6 fix: add image max depth
• 0938fb7 fix: add max_emphasis_depth
• 9946c92 tests: update dealine time for pypy
• 4009f67 fix: use SAFE_PROTOCOLS instead of HARMFUL_PROTOCOLS
• 3025549 Merge pull request #462 from Sanjays2402/fix/markdown-renderer-escape-emphasis
• b042996 fix: escape literal emphasis markers in MarkdownRenderer
• Additional commits viewable in compare view

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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[aaronspring]

Superseded by #467, which re-locked mistune to 3.3.4 — one release past the 3.3.3 this PR targets — so GHSA-6m44-fpc8-c3rq is already closed on main. Merging this now would downgrade the lockfile, so I'm closing it.

For context: #455 bumped mistune to 3.3.0, which turned out to be affected by that same advisory. While verifying, I checked every registry-sourced package in uv.lock against the PyPI advisory data — 147 packages, none affected after #467.

---

Generated by Claude Code

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

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