dependabot[bot] opened a new pull request, #27509: URL: https://github.com/apache/datafusion/pull/27509
Bumps the all-uv-deps group with 1 update: [myst-parser](https://github.com/executablebooks/MyST-Parser). Updates `myst-parser` from 5.1.0 to 5.2.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/executablebooks/MyST-Parser/releases">myst-parser's releases</a>.</em></p> <blockquote> <h2>v5.2.0</h2> <p>Heading anchors are now stable and documented: one shared slug implementation with <code>"github"</code>, <code>"gitlab"</code> and <code>"docutils"</code> presets, slugs emitted as real HTML ids, explicit <code>(target)=</code> ids taking priority, and a versioned anchor contract. Warnings and other tools now get accurate source lines (also inside <code>{include}</code>d files), docutils 0.23 is supported, inputs that used to abort the build now warn instead, and many fixes land for references, images, front matter, substitutions and directives; a new <code>section_ref</code> extension links <code>§1.1</code>-style references to numbered headings.</p> <p>Nothing is dropped: Python <code>>=3.11</code>, Sphinx <code>>=8,<10</code> and the markdown-it-py requirement are unchanged, mdit-py-plugins is raised to <code>~=0.7</code> (it was <code>~=0.6,>=0.6.1</code>), and the docutils range is widened to <code>>=0.20,<0.24</code>. Some of these changes can still alter the output of a project that built before, so please read the upgrade notes.</p> <h3>‼️ Upgrade notes</h3> <ul> <li><strong>Heading anchors</strong> (<a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1158">#1158</a>, <a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1168">#1168</a>), see <a href="https://myst-parser.readthedocs.io/en/latest/syntax/header-anchors.html">docs</a>: <ul> <li>Duplicate heading slugs now get fixed-base suffixes, <code>x</code>, <code>x-1</code>, <code>x-2</code>, as on GitHub; the third and later duplicates used to get <code>x-1-2</code>, <code>x-1-2-3</code>, ... <strong>So a link that uses the old slug of a third or later duplicate, such as <code>[](https://github.com/executablebooks/MyST-Parser/blob/HEAD/#x-1-2)</code>, no longer resolves and warns (<code>myst.xref_missing</code>, which fails a <code>-W</code> build): change it to <code>[](https://github.com/executablebooks/MyST-Parser/blob/HEAD/#x-2)</code>.</strong> Links to the first two duplicates are unchanged, and every HTML id a heading had before is kept.</li> <li>Slugs are also emitted as secondary HTML <code>id</code>s on the rendered headings, so <code>#slug</code> links work in the published HTML. The docutils id stays the primary (first) id, so existing fragment links keep working. Set <code>myst_heading_anchors_html_ids = False</code> to emit only the docutils id.</li> <li>An explicit <code>(target)=</code> placed before a heading becomes the section's primary id, which tocs, permalinks and <code>objects.inv</code> use; the implicit heading id is kept as a secondary anchor.</li> <li>A heading whose slug is empty (a punctuation-only title, or any non-Latin title with the <code>"docutils"</code> preset) gets no anchor, and an empty fragment, <code>[](https://github.com/executablebooks/MyST-Parser/blob/HEAD/#)</code>, now warns as unresolved.</li> <li>Links that used to warn now resolve when the anchor exists: same-document links to implicit ids (such as headings deeper than <code>myst_heading_anchors</code>; under Sphinx only as a last resort), and cross-document links to label ids and to the implicit ids of headings within the <code>myst_heading_anchors</code> depth. <code>[](https://github.com/executablebooks/MyST-Parser/blob/HEAD/doc.md#label)</code> takes the target's title as its text (<a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1207">#1207</a>).</li> <li>These rules (slug presets, deduplication, empty slugs, explicit-id priority and HTML ids) are now a documented contract, pinned by a versioned, language-agnostic corpus (<code>tests/fixtures/slugs.json</code>). <code>myst_parser.mdit_to_docutils.base.default_slugify</code> is deprecated in favour of <code>myst_parser.slugs.github_slugify</code>.</li> </ul> </li> <li><strong>Directive option warnings</strong> (<a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1164">#1164</a>): each warning now points at the offending option's line, and unknown options are reported one per warning, as <code>Unknown option key: 'x' (allowed: [...])</code>, instead of one aggregate <code>Unknown option keys: [...]</code>. The <code>myst.directive_option</code> subtype is unchanged, so <code>suppress_warnings</code> keeps working, but tests that match the old message need updating.</li> <li><strong>Directive API</strong> (<a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1164">#1164</a>): directives now receive the full fenced text as <code>block_text</code>, as in reStructuredText, so errors that echo it show the whole fence; and <code>content_offset</code> is <code>-1</code> when the body starts on the opening line.</li> <li><strong>Source lines</strong> (<a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1164">#1164</a>, <a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1169">#1169</a>, <a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1179">#1179</a>): lines in warnings and nodes change where they were wrong. Text nodes no longer take the line of the most recent directive (so gettext <code>.pot</code> locations change), lines inside <code>{include}</code>d files are no longer one late, and the body of a directive with options and a trailing blank line is no longer one line off.</li> <li><strong>Front matter</strong> (<a href="https://redirect.github.com/executablebooks/MyST-Parser/pull/1197">#1197</a>): options that can only be set globally (<code>heading_slug_func</code>, <code>update_mathjax</code>, <code>mathjax_classes</code>, <code>suppress_warnings</code>, <code>inventories</code>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/executablebooks/MyST-Parser/blob/master/CHANGELOG.md">myst-parser's changelog</a>.</em></p> <blockquote> <h2>5.2.0 - 2026-11-10</h2> <p>Heading anchors are now stable and documented: one shared slug implementation with <code>"github"</code>, <code>"gitlab"</code> and <code>"docutils"</code> presets, slugs emitted as real HTML ids, explicit <code>(target)=</code> ids taking priority, and a versioned anchor contract. Warnings and other tools now get accurate source lines (also inside <code>{include}</code>d files), docutils 0.23 is supported, inputs that used to abort the build now warn instead, and many fixes land for references, images, front matter, substitutions and directives; a new <code>section_ref</code> extension links <code>§1.1</code>-style references to numbered headings.</p> <p>Nothing is dropped: Python <code>>=3.11</code>, Sphinx <code>>=8,<10</code> and the markdown-it-py requirement are unchanged, mdit-py-plugins is raised to <code>~=0.7</code> (it was <code>~=0.6,>=0.6.1</code>), and the docutils range is widened to <code>>=0.20,<0.24</code>. Some of these changes can still alter the output of a project that built before, so please read the upgrade notes.</p> <h3>‼️ Upgrade notes</h3> <ul> <li><strong>Heading anchors</strong> (<a href="gh-pr:1158">gh-pr:1158</a>, <a href="gh-pr:1168">gh-pr:1168</a>), see <a href="https://github.com/executablebooks/MyST-Parser/blob/master/syntax/header-anchors"></a>: <ul> <li>Duplicate heading slugs now get fixed-base suffixes, <code>x</code>, <code>x-1</code>, <code>x-2</code>, as on GitHub; the third and later duplicates used to get <code>x-1-2</code>, <code>x-1-2-3</code>, ... <strong>So a link that uses the old slug of a third or later duplicate, such as <code>[](https://github.com/executablebooks/MyST-Parser/blob/master/#x-1-2)</code>, no longer resolves and warns (<code>myst.xref_missing</code>, which fails a <code>-W</code> build): change it to <code>[](https://github.com/executablebooks/MyST-Parser/blob/master/#x-2)</code>.</strong> Links to the first two duplicates are unchanged, and every HTML id a heading had before is kept.</li> <li>Slugs are also emitted as secondary HTML <code>id</code>s on the rendered headings, so <code>#slug</code> links work in the published HTML. The docutils id stays the primary (first) id, so existing fragment links keep working. Set <code>myst_heading_anchors_html_ids = False</code> to emit only the docutils id.</li> <li>An explicit <code>(target)=</code> placed before a heading becomes the section's primary id, which tocs, permalinks and <code>objects.inv</code> use; the implicit heading id is kept as a secondary anchor.</li> <li>A heading whose slug is empty (a punctuation-only title, or any non-Latin title with the <code>"docutils"</code> preset) gets no anchor, and an empty fragment, <code>[](https://github.com/executablebooks/MyST-Parser/blob/master/#)</code>, now warns as unresolved.</li> <li>Links that used to warn now resolve when the anchor exists: same-document links to implicit ids (such as headings deeper than <code>myst_heading_anchors</code>; under Sphinx only as a last resort), and cross-document links to label ids and to the implicit ids of headings within the <code>myst_heading_anchors</code> depth. <code>[](https://github.com/executablebooks/MyST-Parser/blob/master/doc.md#label)</code> takes the target's title as its text (<a href="gh-pr:1207">gh-pr:1207</a>).</li> <li>These rules (slug presets, deduplication, empty slugs, explicit-id priority and HTML ids) are now a documented contract, pinned by a versioned, language-agnostic corpus (<code>tests/fixtures/slugs.json</code>). <code>myst_parser.mdit_to_docutils.base.default_slugify</code> is deprecated in favour of <code>myst_parser.slugs.github_slugify</code>.</li> </ul> </li> <li><strong>Directive option warnings</strong> (<a href="gh-pr:1164">gh-pr:1164</a>): each warning now points at the offending option's line, and unknown options are reported one per warning, as <code>Unknown option key: 'x' (allowed: [...])</code>, instead of one aggregate <code>Unknown option keys: [...]</code>. The <code>myst.directive_option</code> subtype is unchanged, so <code>suppress_warnings</code> keeps working, but tests that match the old message need updating.</li> <li><strong>Directive API</strong> (<a href="gh-pr:1164">gh-pr:1164</a>): directives now receive the full fenced text as <code>block_text</code>, as in reStructuredText, so errors that echo it show the whole fence; and <code>content_offset</code> is <code>-1</code> when the body starts on the opening line.</li> <li><strong>Source lines</strong> (<a href="gh-pr:1164">gh-pr:1164</a>, <a href="gh-pr:1169">gh-pr:1169</a>, <a href="gh-pr:1179">gh-pr:1179</a>): lines in warnings and nodes change where they were wrong. Text nodes no longer take the line of the most recent directive (so gettext <code>.pot</code> locations change), lines inside <code>{include}</code>d files are no longer one late, and the body of a directive with options and a trailing blank line is no longer one line off.</li> <li><strong>Front matter</strong> (<a href="gh-pr:1197">gh-pr:1197</a>): options that can only be set globally</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/5137add4d72260c99e0c2e9f9a7c2ff8306ec930"><code>5137add</code></a> 🚀 RELEASE: v5.2.0 (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1228">#1228</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/7d48de0b875535c444a4ab9c8013041069be0be2"><code>7d48de0</code></a> ✨ NEW: Add section_ref syntax extension (§1.1 heading references) (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1170">#1170</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/a99fd5e3ac20dfdfe7966c9ea3cdc44b371afa29"><code>a99fd5e</code></a> 📚 DOCS: suppress sphinx-design 0.8.0's design.card_legacy warning (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1229">#1229</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/dde8f25ee4b8284eb7a4e15766ca3859b9cdae5b"><code>dde8f25</code></a> ⬆️ Allow flit_core 4 as build backend (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1185">#1185</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/191565455ecc0204547298a1bcc35b9caa4a7204"><code>1915654</code></a> 🐛 FIX: exact source lines in <code>{include}</code>d files (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1169">#1169</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/253427e8ee12dd9269fa0e9e9aaded39bcfe2659"><code>253427e</code></a> 🐛 FIX: keep validated topmatter config, and enforce <code>global_only</code> (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1197">#1197</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/03ffdcd7b34342e01b0bc5809c7a8a98aadb8370"><code>03ffdcd</code></a> ⬆️ Bump actions/setup-python from 6 to 7 (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1226">#1226</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/d9c999185b154636b31858ec1a04d6a78309bd03"><code>d9c9991</code></a> 🐛 FIX: Allow a {table} caption to wrap onto the following lines (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1195">#1195</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/81b0be5d2e644a3900f949a844854e1e2ba5f830"><code>81b0be5</code></a> 🐛 FIX: Make a document's own front matter available in env.metadata (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1171">#1171</a>)</li> <li><a href="https://github.com/executablebooks/MyST-Parser/commit/fc007855072b61679ae9239de5e75fdcae48e198"><code>fc00785</code></a> 🐛 FIX: Keep link titles through cross-reference resolution (<a href="https://redirect.github.com/executablebooks/MyST-Parser/issues/1196">#1196</a>)</li> <li>Additional commits viewable in <a href="https://github.com/executablebooks/MyST-Parser/compare/v5.1.0...v5.2.0">compare view</a></li> </ul> </details> <br /> [](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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </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]
