dependabot[bot] opened a new pull request, #40389:
URL: https://github.com/apache/superset/pull/40389

   Bumps [markdown](https://github.com/Python-Markdown/markdown) from 3.8.1 to 
3.10.2.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/Python-Markdown/markdown/releases";>markdown's 
releases</a>.</em></p>
   <blockquote>
   <h2>Release 3.10.2</h2>
   <h3>Fixed</h3>
   <ul>
   <li>Fix a regression related to comment handling (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1590";>#1590</a>).</li>
   <li>More reliable fix for <code>&lt;/</code> (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1593";>#1593</a>).</li>
   </ul>
   <h2>Release 3.10.1</h2>
   <h3>Fixed</h3>
   <ul>
   <li>Ensure nested elements inside inline comments are properly unescaped (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1571";>#1571</a>).</li>
   <li>Make the docs build successfully with mkdocstrings-python 2.0 (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1575";>#1575</a>).</li>
   <li>Fix infinite loop when multiple bogus or unclosed HTML comments appear 
in input (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1578";>#1578</a>).</li>
   <li>Fix another infinite loop when handling bad comments (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1586";>#1586</a>).</li>
   </ul>
   <h2>Release 3.10.0</h2>
   <h3>Changed</h3>
   <ul>
   <li>Officially support Python 3.14 and PyPy 3.11 and drop support for Python 
3.9
   and PyPy 3.9.</li>
   </ul>
   <h3>Fixed</h3>
   <ul>
   <li>Fix an HTML comment parsing case in some Python versions that can cause 
an
   infinite loop (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1554";>#1554</a>).</li>
   <li>Revert the default behavior of <code>USE_DEFINITION_ORDER</code> (to 
<code>True</code>). The new
   behavior introduced in 3.9.0 is experimental and results are inconsistent.
   It should not have been made the default behavior (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1561";>#1561</a>).</li>
   </ul>
   <h2>Release 3.9.0</h2>
   <h3>Changed</h3>
   <ul>
   <li>Footnotes are now ordered by the occurrence of their references in the
   document. A new configuration option for the footnotes extension,
   <code>USE_DEFINITION_ORDER</code>, has been added to support restoring the 
previous
   behavior of ordering footnotes by the occurrence of definitions (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1367";>#1367</a>).</li>
   </ul>
   <h3>Fixed</h3>
   <ul>
   <li>Ensure inline processing iterates through elements in document order (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1546";>#1546</a>).</li>
   <li>Fix handling of incomplete HTML tags in code spans in Python 3.14 (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1547";>#1547</a>).</li>
   </ul>
   <h2>Release 3.8.2</h2>
   <h3>Fixed</h3>
   <ul>
   <li>Fix <code>codecs</code> deprecation in Python 3.14.</li>
   <li>Fix issue with unclosed comment parsing in Python 3.14.</li>
   <li>Fix issue with unclosed declarations in Python 3.14.</li>
   <li>Fix issue with unclosed HTML tag <code>&lt;foo</code> and Python 
3.14.</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/Python-Markdown/markdown/blob/master/docs/changelog.md";>markdown's
 changelog</a>.</em></p>
   <blockquote>
   <h2>[3.10.2] - 2026-02-09</h2>
   <h3>Fixed</h3>
   <ul>
   <li>Fix a regression related to comment handling (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1590";>#1590</a>).</li>
   <li>More reliable fix for <code>&lt;/</code> (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1593";>#1593</a>).</li>
   </ul>
   <h2>[3.10.1] - 2026-01-21</h2>
   <h3>Fixed</h3>
   <ul>
   <li>Ensure nested elements inside inline comments are properly unescaped (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1571";>#1571</a>).</li>
   <li>Make the docs build successfully with mkdocstrings-python 2.0 (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1575";>#1575</a>).</li>
   <li>Fix infinite loop when multiple bogus or unclosed HTML comments appear 
in input (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1578";>#1578</a>).</li>
   <li>Fix another infinite loop when handling bad comments (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1586";>#1586</a>).</li>
   </ul>
   <h2>[3.10.0] - 2025-11-03</h2>
   <h3>Changed</h3>
   <ul>
   <li>Officially support Python 3.14 and PyPy 3.11 and drop support for Python 
3.9
   and PyPy 3.9.</li>
   </ul>
   <h3>Fixed</h3>
   <ul>
   <li>Fix an HTML comment parsing case in some Python versions that can cause 
an
   infinite loop (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1554";>#1554</a>).</li>
   <li>Revert the default behavior of <code>USE_DEFINITION_ORDER</code> (to 
<code>True</code>). The new
   behavior introduced in 3.9.0 is experimental and results are inconsistent.
   It should not have been made the default behavior (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1561";>#1561</a>).</li>
   </ul>
   <h2>[3.9.0] - 2025-09-04</h2>
   <h3>Changed</h3>
   <ul>
   <li>Footnotes are now ordered by the occurrence of their references in the
   document. A new configuration option for the footnotes extension,
   <code>USE_DEFINITION_ORDER</code>, has been added to support restoring the 
previous
   behavior of ordering footnotes by the occurrence of definitions (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1367";>#1367</a>).</li>
   </ul>
   <h3>Fixed</h3>
   <ul>
   <li>Ensure inline processing iterates through elements in document order (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1546";>#1546</a>).</li>
   <li>Fix handling of incomplete HTML tags in code spans in Python 3.14 (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1547";>#1547</a>).</li>
   </ul>
   <h2>[3.8.2] - 2025-06-19</h2>
   <h3>Fixed</h3>
   <ul>
   <li>Fix <code>codecs</code> deprecation in Python 3.14 (<a 
href="https://redirect.github.com/Python-Markdown/markdown/issues/1537";>#1537</a>).</li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/e7a0efb3a7c36d6b8005403122705662bc17c904";><code>e7a0efb</code></a>
 Bump version to 3.10.2</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/630183336bda57c258becc3ed229105481876a7e";><code>6301833</code></a>
 Document HTML sanitation policy</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/7f29f1a69d236f5bb11645c2fa03fcf701487c8c";><code>7f29f1a</code></a>
 More reliable fix for <code>&lt;/</code></li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/c4386475a6b6daea43b7d7717add4271adc9a3c1";><code>c438647</code></a>
 Fix regression of special comments</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/e5fa5b86e8ec380cbc520cfc637d72c779e5c601";><code>e5fa5b8</code></a>
 Bump version to 3.10.1</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/f9253495f5d9919f2fdd5e147832b5fc21330f65";><code>f925349</code></a>
 More HTML fixes</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/9933a0a4699f3dea91f46528a2bf54863f531c08";><code>9933a0a</code></a>
 Revert &quot;Allow reference links with backticks&quot;</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/07dfa4eb43f7a2ab3181b4f842a960a03a6c1221";><code>07dfa4e</code></a>
 Allow reference links with backticks</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/fb6b27a6ff90980b5bcb0cd51528a7c9dc3a93ca";><code>fb6b27a</code></a>
 Fix infinite loop when text contains multiple unclosed comments</li>
   <li><a 
href="https://github.com/Python-Markdown/markdown/commit/89112c293f7b399ae8808f3a06306f46601e9684";><code>89112c2</code></a>
 Make the docs build successfully with mkdocstrings-python 2.0</li>
   <li>Additional commits viewable in <a 
href="https://github.com/Python-Markdown/markdown/compare/3.8.1...3.10.2";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=markdown&package-manager=pip&previous-version=3.8.1&new-version=3.10.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to