Bump myst-parser from 4.0.1 to 5.0.0

[dependabot]

Bumps myst-parser from 4.0.1 to 5.0.0.

Release notes

Sourced from myst-parser's releases.

v5.0.0

MyST-Parser 5.0.0

Release Date: 2026-01-15

This release significantly bumps the supported versions of core dependencies:

‼️ Breaking Changes

This release updates the minimum supported versions:

• Python: >=3.11 (dropped Python 3.10, tests up to 3.14)
• Sphinx: >=8,<10 (dropped Sphinx 7, added Sphinx 9)
• Docutils: >=0.20,<0.23 (dropped docutils 0.19, added docutils 0.22)
• markdown-it-py: ~=4.0 (upgraded from v3)

⬆️ Dependency Upgrades

• ⬆️ Upgrade to markdown-it-py v4 by @​chrisjsewell in #1060
• ⬆️ Drop Python 3.10 and Sphinx 7 by @​chrisjsewell in #1059
• ⬆️ Drop docutils 0.19 by @​chrisjsewell in #1061
• ⬆️ Add support for Python 3.14 by @​chrisjsewell in #1075
• ⬆️ Support Sphinx v9 by @​chrisjsewell in #1076
• ⬆️ Allow docutils 0.22 by @​chrisjsewell in #1084

👌 Improvements

• 👌 Improve generation of meta nodes by @​AA-Turner in #1080

📚 Documentation

• 📚 Fix typo in tables.md by @​electricalgorithm in #1034
• 📚 Fix minor typo in cross-referencing.md by @​krassowski in #1036

🔧 Internal / Maintenance

• 🔧 Update pre-commit by @​chrisjsewell in #1058
• 🔧 Add AGENTS.md by @​chrisjsewell in #1083

Full Changelog: v4.0.1...v5.0.0

Changelog

Sourced from myst-parser's changelog.

5.0.0 - 2026-01-15

This release significantly bumps the supported versions of core dependencies:

‼️ Breaking Changes

This release updates the minimum supported versions:

• Python: >=3.11 (dropped Python 3.10, tests up to 3.14)
• Sphinx: >=8,<10 (dropped Sphinx 7, added Sphinx 9)
• Docutils: >=0.20,<0.23 (dropped docutils 0.19, added docutils 0.22)
• markdown-it-py: ~=4.0 (upgraded from v3)

⬆️ Dependency Upgrades

• ⬆️ Upgrade to markdown-it-py v4 by gh-user:chrisjsewell in gh-pr:1060
• ⬆️ Drop Python 3.10 and Sphinx 7 by gh-user:chrisjsewell in gh-pr:1059
• ⬆️ Drop docutils 0.19 by gh-user:chrisjsewell in gh-pr:1061
• ⬆️ Add support for Python 3.14 by gh-user:chrisjsewell in gh-pr:1075
• ⬆️ Support Sphinx v9 by gh-user:chrisjsewell in gh-pr:1076
• ⬆️ Allow docutils 0.22 by gh-user:chrisjsewell in gh-pr:1084

👌 Improvements

• 👌 Improve generation of meta nodes by gh-user:AA-Turner in gh-pr:1080

📚 Documentation

• 📚 Fix typo in tables.md by gh-user:electricalgorithm in gh-pr:1034
• 📚 Fix minor typo in cross-referencing.md by gh-user:krassowski in gh-pr:1036

🔧 Internal / Maintenance

• 🔧 Update pre-commit by gh-user:chrisjsewell in gh-pr:1058
• 🔧 Add AGENTS.md by gh-user:chrisjsewell in gh-pr:1083

Full Changelog: v4.0.1...v5.0.0

Commits

• a139a1f 🚀 Release v5.0.0 (#1085)
• 5405110 [pre-commit.ci] pre-commit autoupdate (#1071)
• 19512c0 ⬆️ Allow docutils 0.22 (#1084)
• a9e529f ⬆️ Support Sphinx v9 (#1076)
• fcf78ca 👌 Improve generation of meta nodes (#1080)
• e0fc7a3 🔧 Add AGENTS.md (#1083)
• 59d5384 ⬆️ Add support for Python 3.14 (#1075)
• 7b7d961 ⬆️ Update pytest requirement from <9,>=8 to >=9,<10 (#1063)
• 3342a3c ⬆️ Update sphinxext-opengraph requirement from ~=0.9.0 to ~=0.13.0 (#1066)
• 2cf85de ⬆️ Update sphinxext-rediraffe requirement from ~=0.2.7 to ~=0.3.0 (#1064)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Resolves #1060
Resolves #1059
Resolves #1061
Resolves #1075
Resolves #1076
Resolves #1084
Resolves #1080
Resolves #1034
Resolves #1036
Resolves #1058
Resolves #1083
Resolves #1085
Resolves #1071
Resolves #1063
Resolves #1066
Resolves #1064

[github-actions]

🤖 Claude Code Review

Code Review Analysis

Summary

This PR bumps myst-parser from version 4.0.1 to 5.0.0 in the documentation requirements. This is a minor dependency update for documentation tooling.

---

Detailed Review

Code Quality ✅

• ✅ Code follows style guide: Not applicable - this is a dependency version update in a requirements file
• ✅ No commented-out code: None present
• ✅ Meaningful variable names: Not applicable
• ✅ DRY principle followed: Not applicable
• ✅ Identify Defects: No bugs, logic errors, or security vulnerabilities introduced. This is a straightforward version bump of a documentation parsing library.
• ✅ Project memory consideration: No .claude/CLAUDE.md exists at the project root (only in build-resources/), so not applicable to this change

Testing ⚠️

• ⚠️ Unit tests for new functions: Not applicable - no new functions
• ⚠️ Integration tests for new endpoints: Not applicable - no new endpoints
• ⚠️ Edge cases covered: Not applicable
• ⚠️ Test coverage > 80%: Cannot verify - this is a documentation dependency. However, it would be advisable to verify that documentation builds successfully with the new version.

Recommendation: Ensure documentation builds pass with myst-parser==5.0.0 before merging.

Documentation ⚠️

• ⚠️ Readme updated if needed: documentation-requirements.txt:2 - The change is self-documenting in the requirements file
• ✅ API docs updated: Not applicable - no API changes
• ✅ Inline comments for complex logic: Not applicable
• ❌ CHANGELOG.md updated: CHANGELOG.md has not been updated to reflect this dependency bump. While this is a minor change, dependency updates should be tracked in the changelog under the [Unreleased] section.
• N/A Markdown formatting: Not applicable to this change

Recommendation: Add an entry to CHANGELOG.md under [Unreleased] section:

### Changed
- Updated myst-parser from 4.0.1 to 5.0.0

Security ✅

• ✅ No hardcoded credentials: None present
• ✅ Input validation implemented: Not applicable
• ✅ Proper error handling: Not applicable
• ✅ No sensitive data in logs: Not applicable
• ✅ License files check: No .lic files found. No AQAAAD strings in relevant project files (the matches found are in build-resources and temp files, not in the actual project code)

---

Final Assessment

Status: ✅ Acceptable with minor recommendations

Critical Issues: None

Non-Critical Recommendations:

1. Update CHANGELOG.md to document this dependency version bump
2. Verify documentation builds successfully with myst-parser==5.0.0

The change itself is clean and follows proper dependency management practices. The version bump from 4.0.1 to 5.0.0 indicates a minor version update which should maintain backward compatibility according to semantic versioning.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

I'll analyze this pull request diff against the code review checklist.

Code Review Analysis

Code Quality

✅ Code follows style guide

• This is a dependency version update in documentation-requirements.txt:2 - no code style issues apply.

✅ No commented-out code

• No commented code present.

✅ Meaningful variable names

• Not applicable - this is a dependency specification file.

✅ DRY principle followed

• Not applicable - this is a dependency specification file.

✅ Identify Defects

• No defects identified. This is a straightforward dependency version bump from myst_parser==4.0.1 to myst_parser==5.0.0.
• Note: This is a major version bump (4.x → 5.x), which may introduce breaking changes. The PR should verify that:
  • Documentation builds successfully with the new version
  • All MyST parser features used in the project still work as expected
  • No deprecated features have been removed that the project depends on

✅ Project memory configuration

• No ./.claude/CLAUDE.md file found in the repository based on the git status.

Testing

⚠️ Testing considerations

• Unit tests for new functions - N/A (dependency update)
• Integration tests for new endpoints - N/A (dependency update)
• Edge cases covered - N/A (dependency update)
• ⚠️ Test coverage > 80% - While not directly applicable, the documentation build should be tested to ensure the major version upgrade doesn't break anything.

Recommendation: Verify that the documentation builds successfully with myst_parser==5.0.0 before merging.

Documentation

✅ Readme updated if needed

• Not required for a dependency update.

✅ API docs updated

• Not applicable.

✅ Inline comments for complex logic

• Not applicable.

❌ CHANGELOG.md updated

• File location: ./CHANGELOG.md (assumed to exist at root)
• The CHANGELOG should document this dependency upgrade, particularly since it's a major version bump.

✅ Markdown files formatting

• Not applicable - this change doesn't affect markdown files.

Security

✅ No hardcoded credentials

• No credentials present.

✅ Input validation implemented

• Not applicable.

✅ Proper error handling

• Not applicable.

✅ No sensitive data in logs

• Not applicable.

✅ No license files (.lic) or AQAAAD strings

• No license files or sensitive strings detected in the diff.

---

Summary

Overall Assessment: ✅ APPROVED with recommendations

This is a clean dependency update with one issue:

Required Action:

1. ❌ Update CHANGELOG.md to document the myst_parser upgrade from 4.0.1 to 5.0.0

Recommended Actions:

1. ⚠️ Test documentation build - Since this is a major version bump (4.x → 5.0.0), verify that all documentation builds successfully and that no MyST parser features have breaking changes
2. ⚠️ Review release notes - Check myst_parser 5.0.0 release notes for any breaking changes that might affect this project

The change itself is straightforward and follows good dependency management practices, but the CHANGELOG should be updated before merging.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

---

Code Review: Bump myst-parser from 4.0.1 to 5.0.0

Summary

This is a dependency version bump PR that updates myst_parser from version 4.0.1 to 5.0.0 in documentation-requirements.txt. This appears to be part of a series of automated dependency updates (based on recent commits showing similar bumps for sphinx-related packages).

---

Review Checklist Results

Code Quality

• ✅ Code follows style guide: N/A - This is a dependency version bump in a requirements file, not code changes
• ✅ No commented-out code: No commented code present
• ✅ Meaningful variable names: N/A - No variables in this change
• ✅ DRY principle followed: N/A - Single line change
• ✅ Identify Defects: No defects identified. The change is straightforward - updating a single dependency version
• ✅ Project memory consideration: No ./.claude/CLAUDE.md file exists in the project root, so nothing to check

Testing

• ⚠️ Unit tests for new functions: N/A - No new functions added
• ⚠️ Integration tests for new endpoints: N/A - No new endpoints
• ⚠️ Edge cases covered: N/A - This is a dependency update
• ❓ Test coverage > 80%: Cannot verify - This is a dependency bump. It would be advisable to verify that documentation builds successfully with the new version

Recommendation: Run the documentation build process to ensure myst_parser 5.0.0 is compatible and doesn't break existing documentation.

Documentation

• ❌ Readme updated if needed: The README files do not appear to require updates for this dependency change
• ❌ API docs updated: N/A - No API changes
• ❌ Inline comments for complex logic: N/A - No code logic
• ❌ CHANGELOG.md updated: The CHANGELOG.md at /home/runner/work/mapper-npi/mapper-npi/CHANGELOG.md:1-30 has not been updated with this dependency change. While minor dependency bumps are sometimes excluded from changelogs, a major version bump (4.x → 5.x) should be documented.
• ✅ Markdown formatting: N/A - No markdown files were modified

Security

• ✅ No hardcoded credentials: None present
• ✅ Input validation implemented: N/A - No input handling
• ✅ Proper error handling: N/A - No code logic
• ✅ No sensitive data in logs: N/A - No logging code
• ✅ No license files checked in: No .lic files or AQAAAD strings present in the diff

---

Summary & Recommendations

Overall Assessment: ✅ Approved with minor suggestions

This is a clean dependency version bump with no critical issues. However:

1. CHANGELOG Update Needed: Consider adding an entry to CHANGELOG.md documenting this major version bump (4.0.1 → 5.0.0):

   ### Changed
   - Bumped myst_parser from 4.0.1 to 5.0.0

2. Testing Recommendation: Verify that the documentation build pipeline succeeds with myst_parser 5.0.0, as major version bumps can introduce breaking changes.

3. Breaking Changes: Review the myst_parser 5.0.0 release notes to identify any breaking changes that might affect your documentation build.

The change itself is minimal and follows proper dependency management practices.

Automated code review analyzing defects and coding standards