RustlingPDF v0.1.6
What's new
Nothing user-facing changed in this release. It carries the first batch of build-pipeline work from a measured audit of where release time and installer bytes go — the audit itself is in the repository at docs/plans/active/build-speed-and-app-size.md.
A smaller Windows setup.exe. 43.6 MiB, down from 44.6. The NSIS installer's LZMA dictionary was raised from the 8 MiB default to 64 MiB so it can see the code the app shell and the processing sidecar have in common. Installing needs about 64 MiB of RAM for decompression, which every supported Windows has.
Slightly larger MSI and deb. 50.1 and 40.9 MiB, up from 49.6 and 40.5. Both binaries now build with thin rather than fat link-time optimisation, which cuts the sidecar's build time by a third at a cost of about 0.2 MB per binary compressed. The MSI and deb have no dictionary lever to offset it, so they carry the cost.
Four unreferenced frontend packages are gone from the dependency manifest. They were never in the shipped bundle, so nothing you download changes.
Upgrading
Nothing to do. No configuration, settings file, or API request shape changed.
Container images
Published to GitHub Container Registry by this release run:
docker pull ghcr.io/hairbui76/rustlingpdf:v0.1.6
docker pull ghcr.io/hairbui76/rustlingpdf-ai-engine:v0.1.6 # optional AI sidecarBoth are also tagged latest. Run instructions: rust/RUNNING_WITH_RUST.md, section "Docker".
Desktop apps
Installers built and signed by this release run, attached below: Linux (.deb; AppImage is paused — coming soon), Windows (-setup.exe — the smaller download — or .msi for msiexec/GPO deployment; pick one and stay on it, updates keep whichever you installed). Each signed bundle has a .sig file next to it so you can verify your download against the project's minisign public key.
At startup the desktop app asks this releases page once whether a newer version exists (Settings -> General turns that off, and has a button for asking on demand); nothing else is ever sent anywhere. Updates install only when you ask, and every download is verified against the signing key first.
Known limitations
No macOS build — that platform is still paused. No AppImage either: v0.1.0 shipped the last one, so an existing AppImage install cannot see this release through its update check and has to be replaced by hand.
Full Changelog: v0.1.5...v0.1.6