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

   Bumps [pymarkdownlnt](https://github.com/jackdewinter/pymarkdown) from 
0.9.36 to 0.9.37.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/jackdewinter/pymarkdown/releases";>pymarkdownlnt's 
releases</a>.</em></p>
   <blockquote>
   <h2>Version 0.9.37 - 2026-05-03</h2>
   <p>Sorry for the long duration between the last release and this release. 
Our small team was enjoying family time with our extended family, with a goal 
to recharge ourselves for the months ahead. In addition, we are going to try 
and release new versions on the first weekend of the month, to try and bring 
regularity to the process.</p>
   <p>After a couple of months of internal testing, we are proud to release 
PML102, which raises a Rule Failure when lists contain lazy continuation lines. 
 This was asked for by a couple of users, and we thought it was a great idea to 
add to PyMarkdown. As a great side effect, the testing for that new Rule 
uncovered a decent number of issues that we fixed as part of adding PML102.</p>
   <p>If you find any more issues with PyMarkdown, please let us know.  We are 
working towards cleaning up our backlog and winnow it down to a much smaller 
list in the next couple of months.</p>
   <h2>Added</h2>
   <ul>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/979";>Issue 
979</a>
   <ul>
   <li>Added Rule Plugin PML102 that raises Rule Failures when lists contain 
lazy continuation lines.</li>
   </ul>
   </li>
   </ul>
   <h2>Fixed</h2>
   <ul>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1482";>Issue 
1482</a>
   <ul>
   <li>addressed weird case where a block quote, at least 4 levels of lists in, 
contains a new list, was generating an assert</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1563";>Issue 
1563</a>
   <ul>
   <li>whitespace differences with new list items in nested containers</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1564";>Issue 
1564</a>
   <ul>
   <li>extra newlines inserted</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1566";>Issue 
1566</a>
   <ul>
   <li>change of indent in list causes issues, making calculations wrong for 
following elements</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1568";>Issue 
1568</a>
   <ul>
   <li>Md046 and Md031 can both fix fenced blocks, so moved to different fix 
levels</li>
   <li>added extra check to make sure that if two fenced code blocks are one 
after the other, first one fixed spacing, not both</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1569";>Issue 
1569</a>
   <ul>
   <li>whitespace was reported in both the list and the paragraph with nested 
containers</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1573";>Issue 
1573</a>
   <ul>
   <li>ContainerTokenManager not handling nested block quotes separated by 
lists</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1574";>Issue 
1574</a>
   <ul>
   <li>in certain nested cases with adjusting indent of a list, the following 
parsing does not take that into account when calculating indentation</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1576";>Issue 
1576</a>
   <ul>
   <li>fixed issue with Md032 not removing a list from the stack after exiting 
the list</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1577";>Issue 
1577</a>
   <ul>
   <li>whitespace for block quotes within a list that has just had a new list 
item added that is indented 1 extra space, was not correct</li>
   </ul>
   </li>
   <li><a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1578";>Issue 
1578</a>
   <ul>
   <li>after correcting <a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1577";>Issue 
1577</a> regeneration was still not adding the proper indentation</li>
   </ul>
   </li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/jackdewinter/pymarkdown/commit/ff2b2a07e0f1943152f5d1dee1361687603e0d3c";><code>ff2b2a0</code></a>
 v0.9.37</li>
   <li><a 
href="https://github.com/jackdewinter/pymarkdown/commit/ab8f65bb3beead4e8fc73b9f8acff14e10a8da68";><code>ab8f65b</code></a>
 Issue 1482</li>
   <li><a 
href="https://github.com/jackdewinter/pymarkdown/commit/36c4f496087920da2de16c817d23803319ddb629";><code>36c4f49</code></a>
 <a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1568";>jackdewinter/pymarkdown#1568</a>
 (<a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1581";>#1581</a>)</li>
   <li><a 
href="https://github.com/jackdewinter/pymarkdown/commit/3fafc978a990838019600e5a0d1f3f18ee782d83";><code>3fafc97</code></a>
 <a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1576";>jackdewinter/pymarkdown#1576</a>
 (<a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1580";>#1580</a>)</li>
   <li><a 
href="https://github.com/jackdewinter/pymarkdown/commit/d83642f505acb4e05ea063b6d93d761380b6c38a";><code>d83642f</code></a>
 Issue 979 (<a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1579";>#1579</a>)</li>
   <li><a 
href="https://github.com/jackdewinter/pymarkdown/commit/6d3c1b70d44ea2202b23552af93aca3b5017ee83";><code>6d3c1b7</code></a>
 v0.9.36 (<a 
href="https://redirect.github.com/jackdewinter/pymarkdown/issues/1558";>#1558</a>)</li>
   <li>See full diff in <a 
href="https://github.com/jackdewinter/pymarkdown/compare/v0.9.36...v0.9.37";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pymarkdownlnt&package-manager=pip&previous-version=0.9.36&new-version=0.9.37)](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