Build: Bump pymarkdownlnt from 0.9.33 to 0.9.34

[dependabot]

Bumps pymarkdownlnt from 0.9.33 to 0.9.34.

Release notes

Sourced from pymarkdownlnt's releases.

Version 0.9.34 - 2025-12-21

Notes

Our team has been working diligently over the past two months to strengthen the foundation of the PyMarkdown Linter. A major milestone is the upgrade of the minimum Python version we test with from 3.9 to 3.10. While we acknowledge that some users may still prefer Python 3.8, we strongly recommend upgrading to 3.10 for improved compatibility, security, and performance. If you are using a version below 3.9 and have a valid reason to stay on that version, please let us know—we’ll explore options to support your needs.

A key feature addition (in response to Issue 1479 ) is the full support for both the disable-next-line pragma and a new mode. This change ensures compatibility with Markdown formatters that add a blank line after HTML comments, as each rule now allows a single blank line between the pragma and the offending line. This update also required us to review and verify all rules to ensure the disable-next-line pragma suppresses issues on the next line effectively. During this process, we identified and fixed 9 critical issues related to pragmas and rule behavior.

Looking ahead, we’re also focused on long-term improvements to our test suite. Over the next six months, we aim to reduce the number of tests while maintaining full code and scenario coverage. As the project has been active for over five years, some tests have remained unchanged for three or more years. Our goal is to refine the test suite to ensure it remains efficient, maintainable, and aligned with our quality standards.

Added

• Issue 1479
  • Support for having a pragma to disable the rule for the next line is extended to include a single blank line between the pragma and the line where the failure occurs.
  • Added large number of tests (see work in fixed section) to ensure that next-line pragmas are consistently working for all rules.
• Issue 1490
  • Added work to measure "extra" test coverage, with goals to keep scenario coverage but reduce redundant code coverage
  • i.e. if two scenarios are different enough but have the same code coverage, have a way to mark them as such

Fixed

• Issue 1426
  • from previous work, but also asked reporter how to enhance this rule
• Issue 1475
  • fixed typo in documentation
• Issue 1505
  • fixed an issue with Md002/Md041 where the bottom of the SetExt token was being reported instead of the top
  • additionally, fixed a small issue with empty documents falsely reporting the end-of-stream token as a "bad" heading
• Issue 1506
  • fixed an issue with Md003 where the bottom of the SetExt token was being reported instead of the top
• Issue 1507
  • fixed an issue with Md023 where the bottom of the SetExt token was being reported instead of the top
• Issue 1508
  • fixed an issue with Md024 where the accumulated text for the Atx Heading and the accumulated text for the SetExt heading with the same text differed
• Issue 1510
  • fixed an issue with Md025 where the bottom of the SetExt token was being reported instead of the top
• Issue 1512
  • adding missing tests for Md043 and SetExt headings
  • fixed an issue with Md043 where the bottom of the SetExt token was being reported instead of the top
• Issue 1514
  • when parsing inline elements from a text block, pragmas were not been considered, resulting in reported lines being off
• Issue 1515
  • Rule Md027 was not adapted to handle Table tokens
• Issue 1516
  • when rewinding a failed LRD that included pragmas, the pragmas were not being rewound themselves, resulting in bad line numbers for any following tokens

Changed

• Issue 1462
  • added system.exclude_path to provide configuration option for the command-line --exclude

... (truncated)

Commits

• 6d356e0 new version (#1526)
• 3e2a070 ensure that all skips have an issue tracking it (#1525)
• 1355a75 jackdewinter/pymarkdown#1522 (#1523)
• a1ba64c Issue 1475 (#1518)
• c87cb4d jackdewinter/pymarkdown#1479 (#1517)
• 5d2572d jackdewinter/pymarkdown#1475 (#1495)
• 737f7da Issue 1462 (#1494)
• e1f2b1a Issue 1462 (#1493)
• 73deab3 jackdewinter/pymarkdown#1462 (#1492)
• 48bb417 jackdewinter/pymarkdown#1490 (#1491)
• See full diff 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)