chore(deps): update dependency pymarkdownlnt to v0.9.29 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pymarkdownlnt (changelog)	==0.9.24 -> ==0.9.29

---

Release Notes

jackdewinter/pymarkdown (pymarkdownlnt)

v0.9.29: Version 0.9.29 - Date: 2025-03-10

Compare Source

The work continues! Due to our development team passing colds back and forth between members, February was a slow month in terms of progress. We plan to start adding the foundations for new leaf items in March and April, in addition to completing the current round of issues found with rule Md031's fix mode.

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!

If everyone reading this can take a moment and think of our mascot, "Bruce" and any pets of their own that have moved on, it would be appreciated. He passed away this morning suddenly. Our team can honestly say that Bruce was the best rubber duck that we have ever had, and we will miss him very much.

Added

• None

Fixed

• Issue 1352
  • Fixed parsing and rehydration issues, as precursor to tackling Md031 fix issue
• Issue 1356
  • Fixed rehydration error with test test_extra_052r0.
• Issue 1358
  • Fixed rehydration error with test test_extra_053d1.
• Issue 1364
  • Fixed parsing error and rehydration error related to multiple drop
    container scenarios involving the remaining containers being lists.
• Issue 1357
  • Fixed issue with rule Md007 and nested lists
• Issue 1371
  • Fixed Md031 fix issues related to issue 1364 fixes.

Changed

• None

v0.9.28: Version 0.9.28 - Date: 2025-02-10

Compare Source

The work continues! Working through the categorized list takes time, but it is well worth it. We are also working on improving our bash and github actions infrastructure, making it easier to release the project each month.

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 1289
  • added documentation under Pre-Commit for how to write the configuration file for Pre-Commit if an alternate extension is needed for the files being scanned
• Issue 1318
  • ported perf_*.cmd scripts to perf_.sh scripts
• Issue 1320
  • added ShFmt .sh formatter to Pre-Commit configuration
• Issue 1322
  • added Shellcheck .sh scanner to Pre-Commit configuration
• Issue 1327
  • added simple mechanism to log and view performance measurements

Fixed

• Issue 1302
  • reported issue where C\# at the end of a header was triggering rule Md020 for no spaces between end mark of an Atx Heading
• Issue 1326
  • fix mode for MD012 not properly handling double lines in lists after new list indicators
• Issue 1288
  • rule Md037 and documentation updated to properly ensure that at least one of the two ends has spaces on both sides of the emphasis sequence
• Issue 1334
  • fixed SNAFU1 for MD031 fix mode, assert
• Issue 1344
  • fixed SNAFU6 for MD031 fix mode, assert
• Issue 1346
  • fixed SNAFU8 for MD031 fix mode, assert

Changed

• Issue 1277
  • Rule Md044 changed to add a code_spans exclusion as a compliment to the code_blocks exclusion.

v0.9.26: Version 0.9.26 - Date: 2024-12-09

Compare Source

Version 0.9.26 - Date: 2024-12-09

Progress continues on locating issues and addressing them, including four issues reported by users. As of this past weekend, (to the best of our knowledge) we have eliminated all fatal issues with Rule Md031 and its fix mode. While there are only three weeks left until the new year, we hope to make significant progress on Rule Md031's fix mode producing incorrect markdown. At the same time, we are starting to do research work into determining the best patterns for introducing new leaf elements in 2025. Our main goal is to provide thorough coverage without sacrificing proper testing. To that end, we will try and figure out and document the best approaches so we can use them for new leaf elements in 2025.

In addition to this work, make solid progress on addressing user issues as reported. And this might seem repetitive, but 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 810
  • Added fix mode for Rule Md012
• Issue 1280
  • Added testing capability to save all single Markdown documents in a specified directory, then scanning them one at a time with PyMarkdown and each of the extensions enabled.

Fixed

• Issue 1259
  • Fixed asserts and bad parsing from cases where containers are added and then a "raw" blank line removes all containers.
• Issue 1263
  • Fixed issue where a new unordered list between two block quotes was not being recognized properly.
• Issue 1270
  • Fixed issue with Md027 not reporting line numbers properly within anything except the first paragraph.
• Issue 1272
  • Parsing of the FCB in certain cases was off, as was the text token containing the code block's text. Resulted in the columns being reported being indented less than expected.
• Issue 1274
  • Fixed remaining assert issues, leaving fixes that produce valid Markdown, but not the intended Markdown.
• Issue 1267
  • Fixed reported issue with task lists creating an error in Md018.
• Issue 1268
  • Fixed issue with Md022 and pragmas, similar to Issue 1208.

Changed

• Issue 1258
  • Moved twine package into dev section

v0.9.25: Version 0.9.25 - Date: 2024-11-07

Compare Source

Version 0.9.25 - Date: 2024-11-07

While it seems like we have been working on the fixing for Rule Md031 forever, that time is starting to come to an end. We have a solid list of what is left to test, and we are confident that we will finish it before the new year. (Hope we did not just jinx ourselves!) As with the last couple of releases, we are testing variations of containers, container starts, and container ends, all to ensure we have confidence that our test scenarios are thorough. At this point, we are very confident with any nesting of up to three containers, will our confidence for nesting scenarios of up to four containers at a high level as well. Following close behind that is our fix mode for Rule Md031 which is the stressor for the nested containers. We are not always happy that we started working on the fix mode for Rule Md031, but we are happy that it uncovered some issues in our parser that we could quickly fix.

But 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 1233
• Issue 1234
• Issue 1235
  • Adding more comprehensive "drop X" tests where multiple levels of containers are involved, and then dropping one or more of those containers in a single line.

Fixed

• Issue 1208
  • Fixed issue with blank lines separated with pragmas not being understood properly.
• Issue 1233
• Issue 1234
• Issue 1235
  • Adding new "drop_x" tests and resolve any scan issues with them.
• Issue 1243
• Issue 1245
  • Handling leading spaces in __fix_spacing function now that data is present.
• Issue 1247
  • In 3+ drop cases with only lists and no block quotes, indent is not calculated properly on rehydrate. This in turn causes the fixed text to be wrong.
• Issue 1250
  • Batch of fixes for cases when Md031 is trying to properly space a fenced code block after dropping 2 containers.

Changed

• Issue 1231)
  • Moved triple nested container tests into their own test_nested_three_* files for better readability.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (2128e86)	619	204	32.96%
Head commit (e9d8fc1)	619 (+0)	204 (+0)	32.96% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#533)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}