build(deps): bump pymdown-extensions from 10.11.2 to 10.21.2

[dependabot]

Bumps pymdown-extensions from 10.11.2 to 10.21.2.

Release notes

Sourced from pymdown-extensions's releases.

10.21. 2

10.21.2

• FIX: Highlight: Latest Pygments versions cannot handle a "filename" for code block titles of None.

10.20.1

• FIX: Quotes: Ensure the first class for callouts (the alert type) is always rendered lowercase.

10.21

• NEW: Caption: Add support for specifying not only IDs but classes and arbitrary attributes. Initial work by @​joapuiib.
• FIX: MagicLink: Fix a matching pattern for Bitbucket repo.

10.20

• NEW: Quotes: New blockquotes extension added that uses a more modern approach when compared to Python Markdown's default. Quotes specifically will not group consecutive blockquotes together in the same lazy fashion that the default Python Markdown does which follows a more modern trend to how parsers these days handle block quotes.

  In addition, Quotes also provides an optional feature to enable specifying callouts/alerts in the style used by GitHub and Obsidian.

10.19.1

• FIX: Arithmatex: Fix issue where block $$ math used inline within a paragraph could result in nested math parsing.

10.19

• NEW: Emoji: Update Twemoji to use Unicode 16.
• NEW: Critic: Roll back view mode deprecation as some still like to use it, though further enhancements to this mode are not planned.

10.18

• NEW: Critic: view mode has been deprecated. To avoid warnings or future issues, explicitly set mode to either accept or reject. In the future, the new default will be accept and the view mode will be removed entirely.
• FIX: Block Admonition: important should have always been available as a default.

10.17.2

• FIX: Blocks: Blocks extensions will now better handle nesting of indented style Admonitions, Details, and Tabbed and other non-conflicting blocks.

10.17.1

• FIX: Fix an issue where Highlight can override another extension in the "registered" list in Python Markdown.

... (truncated)

Commits

• a4fdd73 Skip tag 10.21.1 has we accidentally already used it
• 8afb4cd Docs: Update JS deps
• 7bf5b29 Pygments needs a non-None value for code block title (#2863)
• 20b11eb Fix some spelling and formatting
• c9edba3 Docs: strengthen Snippets warning and add security considerations
• 6d92b68 Bump version
• baeca0e Docs: update JS deps
• bf2a237 Add classes and attributes to captions (#2844)
• 5c69e05 Fix bitbucket reference (#2835)
• fa4a066 Fix spelling
• 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)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

This PR updates the 'pymdown-extensions' dependency to version 10.21.2. The update is up to standards and fixes one existing issue according to automated analysis. There are no security or logic concerns identified. The main action item is to verify that the documentation build and Markdown rendering are unaffected by this version jump.

Test suggestions

• Verify that the MkDocs build process completes successfully with the new extension version.
• Verify that existing Markdown content renders correctly without regression under the new version.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the MkDocs build process completes successfully with the new extension version.
2. Verify that existing Markdown content renders correctly without regression under the new version.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}