Bump markdown-it and markdownlint-cli#45
Merged
Conversation
Bumps [markdown-it](https://github.com/markdown-it/markdown-it) to 14.2.0 and updates ancestor dependency [markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli). These dependencies need to be updated together. Updates `markdown-it` from 13.0.1 to 14.2.0 - [Changelog](https://github.com/markdown-it/markdown-it/blob/master/CHANGELOG.md) - [Commits](markdown-it/markdown-it@13.0.1...14.2.0) Updates `markdownlint-cli` from 0.33.0 to 0.49.0 - [Release notes](https://github.com/igorshubovych/markdownlint-cli/releases) - [Commits](igorshubovych/markdownlint-cli@v0.33.0...v0.49.0) --- updated-dependencies: - dependency-name: markdown-it dependency-version: 14.2.0 dependency-type: indirect - dependency-name: markdownlint-cli dependency-version: 0.49.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
WalkthroughThe Changesmarkdownlint-cli Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 55: The markdownlint-cli version in package.json has been updated to
^0.49.0, but the .pre-commit-config.yaml file still references the older v0.33.0
revision, causing inconsistent linting behavior across development, local
pre-commit hooks, and CI/CD pipelines. Update the rev field for the
markdownlint-cli entry in .pre-commit-config.yaml from v0.33.0 to v0.49.0 to
ensure all execution paths use the same version and produce consistent linting
results.
- Line 55: There is a Node.js version compatibility mismatch in package.json.
The project's minimum Node version requirement is set to >=16.16.0 but the
markdownlint-cli devDependency version 0.49.0 requires Node.js >=22. Update the
engines field in package.json (specifically the node property) from >=16.16.0 to
>=22 to align with the markdownlint-cli 0.49.0 requirement and ensure all
devDependencies can run properly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: ddeae821-d69d-4ab0-92a7-8ef52232d7a5
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
eqrx
approved these changes
Jun 18, 2026
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
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.
Bumps markdown-it to 14.2.0 and updates ancestor dependency markdownlint-cli. These dependencies need to be updated together.
Updates
markdown-itfrom 13.0.1 to 14.2.0Changelog
Sourced from markdown-it's changelog.
... (truncated)
Commits
829797a14.2.0 released9ce2087Fix smartquotes perfomance02e73b8linkify-it bump68cfb8cfix: don't end HTML comment blocks on a blank line (#1155)1083137Readme cleanup97c7ca2Update funding infoc471b55Changelog update7769621isPunctChar => isPunctCharCodeaa2aa70fix: always reset parentType in lheading rule (#1131)59955f2Polish PRs #1072, #1074Updates
markdownlint-clifrom 0.33.0 to 0.49.0Release notes
Sourced from markdownlint-cli's releases.
... (truncated)
Commits
a4d5d37Bump version 0.49.0503f264Delete and recreate package-lock.json via "npm install".7a24593Bump markdownlint from 0.40.0 to 0.41.0c7c1c76Bump commander from 14.0.3 to 15.0.083f5f30Bump tinyglobby from 0.2.16 to 0.2.1774b98deBump js-yaml from 4.1.1 to 4.2.0d368135Bump markdown-it from 14.1.1 to 14.2.0dd34288Bump ava from 8.0.0 to 8.0.11e363dcBump brace-expansion from 5.0.5 to 5.0.62f092d2Bump ava from 7.0.0 to 8.0.0Dependabot 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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.