[skip changelog] Bump markdown-link-check from 3.10.3 to 3.13.7 #2898
Conversation
This file contains hidden or 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
per1234
added
type: enhancement
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.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.mdhas been updated with a migration guide (for breaking changes)configuration.schema.jsonupdated if new parameters are added.What kind of change does this PR introduce?
Update the project's markdown-link-check tool dependency to the latest version.
What is the current behavior?
The markdown-link-check tool is used to check for broken links in the documentation hosted in this repository. This tool is managed via the npm package framework.
Because Dependabot has not been configured to provide updates for the project's npm package dependencies, the markdown-link-check dependency is managed manually, with the expected result that the project is using a significantly outdated version of the tool.
The outdated version of the tool has significant bugs and is missing important enhancements.
What is the new behavior?
The latest version of markdown-link-check is used.
Does this PR introduce a breaking change, and is titled accordingly?
No breaking change.
Other information
Related: #1692