build(deps-dev): bump pymarkdownlnt from 0.9.20 to 0.9.25#353
build(deps-dev): bump pymarkdownlnt from 0.9.20 to 0.9.25#353dependabot[bot] wants to merge 2 commits intomainfrom
Conversation
Bumps [pymarkdownlnt](https://github.com/jackdewinter/pymarkdown) from 0.9.20 to 0.9.25. - [Release notes](https://github.com/jackdewinter/pymarkdown/releases) - [Changelog](https://github.com/jackdewinter/pymarkdown/blob/main/changelog.md) - [Commits](jackdewinter/pymarkdown@v0.9.20...v0.9.25) --- updated-dependencies: - dependency-name: pymarkdownlnt dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesCodacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps pymarkdownlnt from 0.9.20 to 0.9.25.
Release notes
Sourced from pymarkdownlnt's releases.
... (truncated)
Commits
2a59cabVersion 0.9.25 (#1254)fe26f2cjackdewinter/pymarkdown#1208 (#1253)2a9931ejackdewinter/pymarkdown#1250 (#1251)50a1e94jackdewinter/pymarkdown#1247 (#1248)cee1f3fjackdewinter/pymarkdown#1245 (#1246)911e871jackdewinter/pymarkdown#1233 (#1241)3335836jackdewinter/pymarkdown#1231 (#1232)f21de30Version 0.9.24 (#1228)41bcdaeUpdating API Documentation (#1227)2bce8caFixing Md031 issues with fixes and deeply nested containers. (#1225)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)