What changed in ReadMD v2.3.7-beta.4.

This beta tightens presentation isolation, update integrity, startup resource loading, and tab feedback while keeping your Markdown as the canonical file.

ReadMD desktop interface showing a formatted Markdown document beside its outline.

Release highlights and boundaries

  1. Safer presentation path

    In-app Reveal.js loads same-origin offline resources; slide HTML passes through whitelist sanitization.

  2. Integrity-first updates

    Official assets download to a fixed directory, pass SHA-256, publish atomically, and are rechecked before execution.

  3. Lighter interaction

    Entry scripts load in stages, shared resources load on demand, ETag revalidation reduces repeat transfers, and search Enter keeps focus.

  4. Clear tab state

    Selection and ARIA state refresh immediately, stale render results are discarded, overflow finds the active tab, and Zen mode keeps one Escape path.

Beta.4 release questions

Is v2.3.7-beta.4 production ready?

No. This is a beta. It is suitable for testing and feedback, but you should keep backups and verify checksums before installation.

Does display repair change my Markdown?

No. Rendering repairs affect the in-memory display. Source bytes change only when you explicitly edit and save the document.

How are updates checked?

Updates come from official GitHub Release assets into a fixed directory, use temporary files and SHA-256 verification, then publish atomically and recheck before execution.

Which platforms receive packages?

Windows, macOS Intel and Apple Silicon, Linux x86_64, UOS, Kylin AMD64 and ARM64 receive packages; HarmonyOS NEXT remains a DevEco source project.