Skip to content

chore(deps): update pre-commit hook jackdewinter/pymarkdown to v0.9.36#424

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/jackdewinter-pymarkdown-0.x
Mar 29, 2026
Merged

chore(deps): update pre-commit hook jackdewinter/pymarkdown to v0.9.36#424
renovate[bot] merged 1 commit intomainfrom
renovate/jackdewinter-pymarkdown-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 29, 2026

This PR contains the following updates:

Package Type Update Change
jackdewinter/pymarkdown repository patch v0.9.34v0.9.36

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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.36: Version 0.9.36 - 2026-03-15

Compare Source

In this release, we’ve invested heavily in revamping our documentation so that you can get from installation to your first useful scan more quickly. After the last release, a backlog review made it clear that our documentation needed an overhaul, especially for people seeing PyMarkdown for the first time. Over time, we added new sections and details without a full restructuring, which made it harder for new users to see where to start and how everything fits together.

We updated the main documentation and introduced new Quick Start guides for common workflows. We simplified each section and reorganized the content so related topics are grouped together and easier to follow. Each Quick Start guide focuses on a single topic, helping new users get productive with PyMarkdown as quickly as possible. New users can now go from install to scanning a repository in just a few minutes. Existing users should find it easier to jump straight to the commands and options they need.

Going forward, you can expect faster scans, clearer error reporting, and continued improvements to the documentation. To support that, our primary goal is to deliver requested features and respond quickly to reported issues, particularly in the rule set, configuration, and documentation. Behind the scenes, we are reducing skipped tests, working through backlogged issues, and investing in refactoring and performance analysis. This work helps keep PyMarkdown fast and dependable as it grows.

Added
  • Issue 1511
    • Added plugins.per-file-ignores.* configuration items to allow for rules to be disabled by matching against a glob-path.
  • Issue 1535
    • Added documentation under the extensions section to provide information on the tables extension.
Changed
  • Issue 1527
    • Updated documentation to give more examples, including examples of TOML configurations.
  • Issue 1539
    • Did full sweep through existing documentation, to clean up.
  • Issue 1555
    • Badges were out of sync, needed new mechanism to properly fetch

v0.9.35: Version 0.9.35 - 2026-01-24

Compare Source

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.

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone Europe/Amsterdam, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot requested a review from a team as a code owner March 29, 2026 01:49
@renovate renovate bot added the pre-commit label Mar 29, 2026
@sonarqubecloud
Copy link
Copy Markdown

@renovate renovate bot merged commit 3494b2c into main Mar 29, 2026
23 checks passed
@renovate renovate bot deleted the renovate/jackdewinter-pymarkdown-0.x branch March 29, 2026 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants