fix markdownlint pre-commit checks #365
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A deprecation warning in the downstream markdownlint package causes the pre-commit checks to fail. The workaround is to use an LTS version of Node for running the checks, as deprecation warnings are not generated. Related GitHub Issues: - igorshubovych/markdownlint-cli#437 - DavidAnson/markdownlint#1032
automatically generated with pre-commit autoupdate
jarkenau
force-pushed
the
fix-markdownlinter
branch
from
22cd1c9 to
c8016bf
Compare
Mark-Niemeyer
approved these changes
Jan 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes:
markdownlintpre-commit checks caused by a deprecating warning in non-LTS version of Node.js.