Release

v1.1.0 release evidence

Inspect the demo, adoption, installation, site, SEO, test, and publication gates for RusDox v1.1.0.

View Markdown source

Published on 2026-09-01 from source commit b3a30b3, tagged v1.1.0. This release adds the verified first-run demo and tightens the public adoption, installation, documentation, and discoverability surfaces without changing the frozen v1 document, template, renderer, or protocol contracts.

Try it

cargo install rusdox --version 1.1.0 --locked
rusdox demo rusdox-demo

The demo refuses an existing destination. A successful run leaves the editable DOCX, directly rendered PDF, page snapshot, and HTML/JSON parity reports together under rusdox-demo/output/.

Contract identity

SurfaceRelease value
Rust crate and CLI1.1.0
Document spec1
Word template syntax1
Renderer API1
Local protocol1
MSRVRust 1.88.0

The release is additive. rusdox demo [directory] composes existing authoring, rendering, and 21-check parity APIs into a safe first success; it refuses any existing destination rather than merging into or overwriting user files.

Local release-candidate evidence

  • 240 Rust tests passed: 160 library, 10 binary, 39 CLI, 25 integration, and 6 rustdoc tests. The CLI count includes artifact creation and overwrite refusal for rusdox demo.
  • cargo fmt --check and strict all-target/all-feature Clippy passed for rusdox 1.1.0.
  • cargo package and cargo publish --dry-run packaged and verified 122 files at 1.7 MiB without uploading.
  • A manual isolated rusdox demo run produced a non-empty editable DOCX, native PDF, HTML/JSON parity evidence, and deterministic page snapshot with all 21 checks passing; its temporary directory was then removed.
  • The checksum-verifying Unix installer fixture installed and executed rusdox 1.1.0 while proving that no user configuration file was created. The tag workflow repeated signed-asset installer checks successfully on Linux, macOS, and Windows.
  • cargo audit --deny unsound passed with no vulnerability or unsoundness rejection. The two allowed unmaintained warnings for rustybuzz 0.20.1 and ttf-parser 0.25.1 retain their dated v1.2.0/2026-12-01 review deadline.
  • The complete generated-site gate passed with 61 HTML pages and 314 bundled files. It checks every internal file reference, all public canonical targets, every sitemap target, the JavaScript-independent homepage evidence, and all Markdown targets in llms-full.txt.
  • Playground, signed registries, GitHub Action, Node/Python/Go integration, stable-contract, 31-capability compatibility, accessibility, benchmark, reproducible-packaging, contributor, and security source gates passed.

Adoption and discoverability changes

  • rusdox demo is now the first README and getting-started success path.
  • Release installers no longer create or modify user configuration; explicit config initialization remains available after install.
  • GitHub Action examples pin the reviewed v1.0.0 commit and default to no write permission, report retention, or PR comment.
  • The README names the exact dual-output/parity wedge, links real artifacts, presents versioned benchmark evidence, and keeps incomplete viewer and PDF conformance work explicit.
  • Homepage documentation and six real example cards are present in HTML before JavaScript runs. External font requests were removed, real output is visible above the fold, and the obsolete sub-second claim was replaced by the checked-in host-separated protocol.
  • The sitemap now includes the playground, signed v1 registry, performance budgets, and three canonical template parity reports. Duplicate legacy and evidence copies are noindex,follow, and their canonical destinations are shipped in the bundle.
  • The AI-readable documentation corpus uses absolute public or repository URLs and has no unresolved relative Markdown links.

Publication evidence

  • The final branch candidate passed Rust CI on Linux, macOS, and Windows, including MSRV 1.88, fuzz-target compilation, deterministic two-build receipts, installer fixtures, and the complete static documentation gate. CodeQL also passed on the same source commit.
  • The v1.1.0 release workflow passed public-API SemVer analysis, generated four reproducible platform archives, published checksums, an SPDX SBOM and signed provenance, then smoke installed the released assets on Linux, macOS, and Windows.
  • The GitHub Release is public with 10 assets. An independent post-publication download verified every SHA256SUMS entry and all four two-build reproducibility receipts.
  • rusdox 1.1.0 on crates.io is published and not yanked. docs.rs had not finished processing the crate at the time of this receipt and remains a CDN/build propagation check rather than a claimed success.
  • The refreshed site bundle was pushed to the Pages repository at 34999fa before this final receipt update; a final publication follows this commit.
  • GitHub metadata now describes the editable DOCX, directly rendered PDF, and parity-evidence wedge and uses focused Rust/document/template/privacy topics.
  • Fresh Chrome rendering passed on desktop and at an exact 390 × 844 CSS-pixel viewport with no console errors and scrollWidth === innerWidth. The first narrow-screen inspection exposed clipped primary-navigation links; the post-release main-branch fix now presents all six destinations in a visible two-row grid and the repeated 390 px screenshot passed.

Release intent

This release does not claim full OOXML coverage, universal Word/PDF viewer fidelity, PDF/A, PDF/UA, tagged PDF, or complete product parity with Pandoc, Typst, Docxtemplater, or lower-level DOCX libraries. Its claim is narrower and testable: supported structured specs or Word templates can produce an editable DOCX, directly rendered PDF, and inspectable parity evidence in one local pipeline.