Small fixes that add up
This release brings together the fixes shipped since 6.6.0: fewer false alarms from the checker, more reliable section links, and small improvements to installation, translations, tabs, and release notes.
Trust the check before you deploy
rdx check now recognizes links to translated homepages, localized search
indexes, llms.txt, and the Markdown exports generated for existing pages and
release notes. Valid links to these endpoints no longer stop your build.
Unknown languages and missing exports are still reported.
The checker also catches problems that can be easy to miss locally:
- Public asset paths must match the capitalization on disk, including every folder and the navbar logo. A path that happens to work on Windows should not break when you deploy on Linux. When there is one clear match, the check suggests the correct URL.
- Duplicate section IDs are reported at the later occurrence, including a
manual ID that collides with a generated heading ID. Repeated Markdown
headings remain valid: RDX gives them distinct IDs such as
setupandsetup-1. - Titles containing footnote references now use the same section IDs in the checker and the rendered page.
See Checking documentation for the validation rules.
Search results should take you to the right section
A footnote reference in a heading adds its displayed number to that heading's ID. Search now accounts for that number, repeated references, and duplicate headings. Clicking the result takes you to the section that actually exists, in both Markdown and MDX pages.
Keep tab behavior when you copy a page
The {disabled} tab marker now works in .md files as it already did in
.mdx. The tab stays visible but cannot be selected, and the first enabled
tab opens automatically. Content from disabled tabs stays out of the search
index.
Copy this page and View Markdown also preserve the marker, so copying an example does not silently enable a disabled tab. Escaped markers and inline code remain literal text.
See Tabs for the syntax.
Keep translated homepages working across editors
Homepage catalogs saved as UTF-8 with BOM are now accepted. Previously, that
encoding marker could make RDX ignore the translations and prevent
rdx i18n sync from updating the catalog. Existing translations and metadata
are preserved when missing phrases are added.
See Languages for the translation workflow.
Put stable releases ahead of their betas
The changelog still lists notes by date, newest first. When dates match, it
now uses semantic version precedence: 1.2.0 comes before 1.2.0-rc.1, which
comes before 1.2.0-beta.2. A +build suffix does not change that order.
Malformed versions are rejected both by the changelog command and when reading
handwritten notes.
The feed button also copies the RSS URL and confirms the copy, ready to paste into your feed reader.
A smoother first installation
The creator reads pnpm 12 progress from both output streams, keeping the
installation display up to date. Starter documentation includes the links
needed to pass rdx check without warnings, and its Next.js minimum matches
the runtime's requirement of 16.4.6.
See Updating RDX for the update commands.