fix: crowdin MDX heading anchor handling#488
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (152)
📝 WalkthroughWalkthroughRefactors Crowdin config and scripts, then normalizes MDX anchor syntax in Unraid OS release notes across English and i18n (de, es, fr, zh). No content changes beyond heading anchors; adds/updates select subsection anchors and internal links. ChangesDocs anchors and Crowdin integration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
unraid-docs | 30a1983 | Commit Preview URL Branch Preview URL |
May 24 2026, 03:19 AM |
Summary
Fix the Crowdin release-note generation path so
.mdrelease-note sources are parsed as MDX and translated explicit heading anchors stay in MDX-safe comment form..mdand.mdxdocs mappings to usemdx_v2_4.mdso existing raw links do not break{#anchor}ids, and HTML-comment anchors--branch mainRoot Cause
The release-note
.mdfiles were stored in Crowdin as plain Markdown sources. Crowdin then escaped or malformed MDX heading anchor comments on export. Recreating the release-note source records as MDX parser records fixed the generation path without renaming files to.mdx.Validation
pnpm exec crowdin config lint --config crowdin.ymlgit diff --check origin/main...HEAD -- crowdin.yml package.json docs/unraid-os/release-notes i18nmdx_v2parser version4de/6.12.4,de/7.0.0,fr/7.2.0, andzh-CN/7.2.0returned clean anchorsFull build intentionally not run per repo guidance.
Summary by CodeRabbit
Documentation
Chores