[dependabot]

Bumps pymdown-extensions from 12.2 to 12.3.

Release notes

Sourced from pymdown-extensions's releases.

12.3

• NEW: BetterEm: Expose a way to disable CommonMark punctuation rules in BetterEm if desired via a new punctuation option.

Commits

• 24ae2b3 Fix link
• f19f2d1 Allow disabling CommonMark punctuation rules in BetterEm
• See full diff 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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 8465513d-f2fd-4c63-ad2d-329b9818880a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
pip/pymdown-extensions	12.3	Unknown	Unknown

Scanned Files

• docs/requirements.txt

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	✅ 0 (≤ 100 complexity)
Duplication	✅ 0 (≤ 1 duplication)

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[SamErde]

Recommendation: merge after the shared CI failure is resolved. This is a narrow pymdown-extensions 12.2 -> 12.3 update: the direct requirement and hash-locked requirement agree, and the release adds an opt-in BetterEm punctuation setting rather than changing the configured behavior. The PR's existing checks are green, including the docs build and dependency review, but they ran on October 23; six newer Dependabot PRs currently fail Codacy SARIF upload, so I am pausing the entire merge sequence rather than relying on stale green checks.

Planned order: #264 -> #268 -> #269 -> #270 -> #271 -> #272 -> #273. There is no apparent functional dependency requiring this order; oldest-first is deterministic. #264 and #270 both modify docs requirement files, so rebase #270 after earlier merges to preserve both pins and hashes. Request @dependabot rebase on each subsequent PR and wait for fresh successful checks before merging.