Build: Bump pymarkdownlnt from 0.9.33 to 0.9.35

[dependabot]

Bumps pymarkdownlnt from 0.9.33 to 0.9.35.

Release notes

Sourced from pymarkdownlnt's releases.

Version 0.9.35 - 2026-01-24

This release was all about starting to clean up some long lingering items that had been on the to-do list for a while. Before addressing Issue 1503, the file scanning code was moved out to the application_file_scanner project. This allowed our team to define a clean separation of responsibilities between the file scanning and the linting, something that we started with the application_properties package. We had started that a while ago, so it was nice to be able to complete that task and to include the --respect-ignore functionality into that new package.

Our main goal for the next couple of months is to address new features and issues as they arise. However, we hope to have enough time to reduce the number of skipped tests and backlogged issues in the repository, while also working on more refactoring and performance analysis. I hope this helps you see the direction that we are taking this repository in!

Added

• Issue 1503
  • Added support for --respect-gitignore flags to respect any Git directories and their .gitignore files.

Fixed

• Issue 1484
  • Made change in application_properties package to properly apply section header when using the --config flag.
  • Added tests to this repository to verify that both implicit and explicit TOML files can be used.

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

... (truncated)

Commits

• c5755e2 Version 0.9.35 - 2026-01-24 (#1534)
• daa6346 Issue 1503, 1484
• 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)
• 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 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)