RustlingPDF v0.1.3

What's new

"Update and restart" no longer needs two clicks. On Windows the first click could report "The update could not be installed" while a second click, with nothing else changed, installed it — the download crossing a cold CDN edge or a proxy, an antivirus scanner holding the freshly written installer, a resource handle that stopped resolving. One click is now worth two attempts, so a fault like that is absorbed instead of shown to you.

There is no risk of installing twice: on Windows the installer replaces the running process, so an attempt that got that far never comes back to be retried. Reaching the retry is itself proof that nothing was installed.

When an update genuinely cannot install, the banner now says why. The reason previously went only to a developer console that a packaged app gives you no way to open, which left "could not be installed" as the whole story.

Upgrading

One caveat worth knowing: the thing fixed in this release is the updater, and the updater that runs is the one in the version you are already on. Upgrading onto 0.1.3 may still take the two clicks it took before. Every upgrade after this one should take one.

Container images

Published to GitHub Container Registry by this release run:

docker pull ghcr.io/hairbui76/rustlingpdf:v0.1.3
docker pull ghcr.io/hairbui76/rustlingpdf-ai-engine:v0.1.3   # optional AI sidecar

Both 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); 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.2...v0.1.3