chore(deps): bump mistune from 3.3.2 to 3.3.3

[dependabot]

Bumps mistune from 3.3.2 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

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.

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)

[amrit110]

Automated fix applied and PR merged

The agentic fix loop successfully fixed this PR and merged it.

✓ Successfully fixed merge_only failures - Modified 0 files - Executed 35 agent actions - (16 info, 9 tool_call, 1 error, 7 tool_result, 2 reasoning)

View detailed trace on dashboard | Raw trace

AI Engineering Maintenance Bot