[Snyk] Security upgrade mistune from 3.0.2 to 3.3.0

[anaconda-security-bot]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• docs/doc-requirements.txt

⚠️Warning

jupyter-client 7.4.9 requires pyzmq, which is not installed.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note:You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[anaconda-security-bot]

This minor version upgrade for mistune from 3.0.2 to 3.3.0 introduces several security enhancements and bug fixes, but no direct API breaking changes.

Key Changes:

• Security Hardening: Version 3.3.0 includes multiple fixes for potential Regular Expression Denial of Service (ReDoS) vulnerabilities (CWE-400) and blocks unsafe URL schemes. These changes result in stricter parsing of links and other elements.
• Behavioral Fixes: Earlier versions in this range introduced minor behavioral changes, such as adjustments to HTML URL escaping and how block quotes are handled on empty lines.

Assessment:
While no mandatory code changes are required, the increased strictness in parsing to address security vulnerabilities could alter the output for certain edge-case Markdown inputs. This warrants a medium risk level, as applications relying on the previous, more lenient parsing behavior may be affected.

Recommendation:
It is recommended to test the Markdown rendering after the upgrade, particularly if your application processes complex or user-provided content, to ensure the stricter parsing does not negatively impact output.

Source: Mistune Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.