Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): update pymarkdownlnt requirement from 0.9.25 to 0.9.26 in /tools in the pip group #209

Merged
merged 4 commits into from
Dec 20, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 10, 2024

Updates the requirements on pymarkdownlnt to permit the latest version.
Updates pymarkdownlnt to 0.9.26

Release notes

Sourced from pymarkdownlnt's releases.

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

Changelog

Sourced from pymarkdownlnt's changelog.

Change Log

This changelog is kept here for historical purposes. For the current changelog, goto our documentation site.

Version 0.9.19 - Date: 2024-04-30

This release focuses on getting the documentation up to date and in the new read-the-docs format. Some small issues were addressed, but this is mainly to get the documents into good shape for release.

To view the new documentation, goto ReadTheDocs.

Added

  • Issue 801
    • Started movement of docs from README.md and docs directory to the newdocs directory with a shorter README.md.
  • Issue 1059
    • Complete redo of pre-commit documentation.
  • Issue 1070
    • Complete redo of advanced configuration documentation.

Fixed

  • None

Changed

  • Issue 1031
    • went through code base and used if/else expressions where possible
  • Issue 1033
    • went through tests for Md007, add some extra tests to cover missed scenarios
  • Issue 1037
    • replaced calls to collect/extract ParserHelper functions followed by asserts with X_verified functions that do that already
  • Issue 1039
    • ensure that all asserts have a message with their reasoning
    • verify that the asserts are required, refactoring where necessary

Version 0.9.18 - Date: 2024-03-18

Added

  • Issue 990
    • added ability to use a TOML file in pyproject.toml format with the --config command line flag

... (truncated)

Commits

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Updates the requirements on [pymarkdownlnt](https://github.com/jackdewinter/pymarkdown) to permit the latest version.

Updates `pymarkdownlnt` to 0.9.26
- [Release notes](https://github.com/jackdewinter/pymarkdown/releases)
- [Changelog](https://github.com/jackdewinter/pymarkdown/blob/main/changelog.md)
- [Commits](jackdewinter/pymarkdown@v0.9.25...v0.9.26)

---
updated-dependencies:
- dependency-name: pymarkdownlnt
  dependency-type: direct:production
  dependency-group: pip
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Dec 10, 2024
cpswan
cpswan previously approved these changes Dec 10, 2024
@XavierChanth XavierChanth merged commit a46c955 into trunk Dec 20, 2024
3 checks passed
@dependabot dependabot bot deleted the dependabot/pip/tools/pip-09a1b88377 branch December 20, 2024 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants