Update pre-commit hook jackdewinter/pymarkdown to v0.9.34

[konflux-internal-p02]

This PR contains the following updates:

Package	Type	Update	Change
jackdewinter/pymarkdown	repository	patch	v0.9.29 -> v0.9.34

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

---

Release Notes

jackdewinter/pymarkdown (jackdewinter/pymarkdown)

v0.9.34: Version 0.9.34 - 2025-12-21

Compare Source

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
• Issue 1504
  • clarified documentation for rule Md001 and the first heading of a document
• Issue 1522
  • properly assigned line/column numbers to table elements, and ensured that all table tokens were properly serializing their relevant data, to allow sight reading of their contents

v0.9.33: Version 0.9.33 - 2025-10-22

Compare Source

Notes

This release was a long time in coming, mostly because of things that are not
immediately obvious. Our team took some time to look and experiment with some
other Python tools, with the aim of reducing the test count for the project
without sacrificing coverage. In addition, we have started to look at the
performance of the project, and how to best accomplish those improvements. Through
the end of the year, we have concrete plans to address any new issues, reduce the
test count while maintaining quality, finishing Issue 1468,
and working on performance enhancements.

Added

• None

Fixed

• Issue 1468
  • started effort to harmonize the LRD and Table tests
  • mapped out level 0 and level 1 container tests for LRDs, adding extra tests
    where necessary

Changed

• None

v0.9.32: Version 0.9.32 - 2025-08-12

Compare Source

Version 0.9.32 - 2025-08-12

The last month has featured our team banging our collective heads against the wall as we work on tightening up the outstanding skipped tests. While there are a couple of stray parsing bugs here and there, most of it has to do with ensuring that the parsing of Markdown tokens are complete... including whitespaces. This is not an issue for generating HTML, but we feel it is a big issue for people writing rules against those tokens. As such, we are trying to ensure we capture as many scenarios as possible, and making sure all tests pass. Its often a tough job, but we feel it is worth it!

On that note, please note that if you are using pragmas to temporarily turn off rules in your documents, there is a small change. In fixing Issue 1447, we noticed there was an issue with how the pragmas ended. To fix this properly, as of release 0.9.32, pragmas starting with a <!-- must end with a --> and pragmas starting with a <!--- must end with a --->. This should be a one time change, and we apologize in advance for any issues it causes.

A big thanks to our users who are reporting issues with the project! While we would like to believe we can think of every test case, we know we cannot. Therefore, we continue to need our users to help us out. If you are scanning any Markdown documents and the results seem off, please file an issue. If you are starting to use our fix mode on your Markdown documents and there are issues, please file an issue. We appreciate any help that we can get to improve the project for everyone!

Added

• Issue 1454
  • added support for --enable-extensions to the command line and API
• Issue 1455
  • added API functions for --no-json5 and --continue-on-error to achieve parity with command line

Fixed

• Issue 1387
  • fixed weird indent issue with Md005
• Issue 1400
  • addressed issues with Md041 and how it handles HTML Block elements at the start of a document
  • added extra examples to documentation to expand on some interesting areas with the Md041 rule and "invisible" tags
• Issue 1441
  Issue 1443
  • an invalid LRD, started right after a container block was started did not unwind properly
• Issue 1446
  • multiple issues with LRDs and whitespace/tabs
• Issue 1447
  • was not handling ---> properly at the end of pragmas
• Issue 1464
  • adding better support for tabs with LRDs.

v0.9.31: Version 0.9.31 - 2025-07-11

Compare Source

Life caught up with our development team this last two months, but we finally finished the work we intended to do for this release. After spending some time to upgrade application_properties to 0.9.0, this release of PyMarkdown adopts that new version, including the simplified setup that was added to application_properties. In addition, PyMarkdown is not using the JSON5 support from application_properties and defaults to it being on. While completing that work, we also went through the configuration documentation, delegating any duplicated sections with the application_properties documentation to application_properties .

During this time, we did some internal housekeeping. We maintain a small group of packages, with common scripting and support to help our team use best practices across all packages. That had not been maintained lately, so we chose to spend a couple of weeks working on getting the packages back to where we wanted them. No effect for how you use this package, but it helps us keep things current.

A big thanks to our users who are reporting issues with the project! While we would like to believe we can think of every test case, we know we cannot. Therefore, we continue to need our users to help us out. If you are scanning any Markdown documents and the results seem off, please file an issue. If you are starting to use our fix mode on your Markdown documents and there are issues, please file an issue. We appreciate any help that we can get to improve the project for everyone!

Added

• Issue 1378
  • upgrade to latest version of application_properties, v0.9.0
  • enabled ability to use JSON5 (default) or normal JSON via command line
    switch
  • made small modifications to plugins as our team is unaware of any
    custom plugin users
    • change is to use a local MyApplicationPropertiesFacade which
      provides better abstraction
  • removed redundant configuration documentation in favor of pointing
    links at updated application_properties documentation
• Issue 1427
  • Adhering to project templates across various projects.

Fixed

• None

Changed

• None

v0.9.30

Compare Source

Version 0.9.30 - Date: 2025-04-19

Apologies for a late release, but we wanted to get some outstanding issues resolved before the release. Notable things to mention are:

• Blanket disabling and then selective enabling of rules
• New pragma disable and enabled commands
• Exclusion of specific files and glob file paths from scanning

And while it may not be visible, a lot of work has been completed on getting proper Table token support in the application. As the rules engine is largely token based, any desired rules that include tables must rely on well-tested support for the new table token. Our development team is hoping to make more progress on this in the next couple of months, and will announce it loudly when it is completed!

A big thanks to our users who are reporting issues with the project! While we would like to believe we can think of every test case, we know we cannot. Therefore, we continue to need our users to help us out. If you are scanning any Markdown documents and the results seem off, please file an issue. If you are starting to use our fix mode on your Markdown documents and there are issues, please file an issue. We appreciate any help that we can get to improve the project for everyone!

Added

• Issue 1396
  • Support for specific rule enablement
  • Disabling of all rules and then selective enabling
• Issue 1401
  • Ability to exclude files from the command line
• Issue 1403
  • Added disable and enable for pragmas

Fixed

• Issue 1379
  • Fixed rehydration issues for test_extra_052l* and test_extra_052m*
  • Precursor for addressing the fix mode Md031 tests
• Issue 1380
  • Fixing the 2 Md031 tests now unblocked from Issue 1379
• Issue 1387
  • Fixed Md005 not firing properly within alternating ordered and unordered list
• Issue 1401
  • Fixed a small issue with the ** glob characters not working properly

Changed

• None

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.