Add v0.1.71 preview release notes
Gitea/pdf-presenter/pipeline/head There was a failure building this commit Details

This commit is contained in:
Dandaedre 2026-11-20 11:55:00 +01:00
parent 9894d6abbe
commit 3724775d30
2 changed files with 31 additions and 0 deletions

View File

@ -4,6 +4,9 @@
### 0.1.71
- Prepare the 0.1.71 preview release with Linux/Windows x86_64 packages; see
[release notes](development/release-notes/v0.1.71.md).
- Run automatic disk-cache cleanup once at startup, after initial document/notes
loading and slide preparation finish, instead of every minute. Preferences edits
no longer trigger scans; manual expunge remains available. Startup cleanup uses

View File

@ -0,0 +1,28 @@
# PDF Presenter 0.1.71 preview
This preview adds disk-cache controls in **Menu → Preferences → Disk cache**.
Set a maximum total size (default **10 GiB**) and lifetime (default **30 days since
rendering**), or use **Expunge unused cache now** to reclaim space manually.
Automatic cleanup runs **once at startup, after initial document loading, notes
loading and slide preparation finish**. There are no periodic scans during the
session. Cleanup removes expired artifacts and then the oldest files to meet the
size target. Active decks are protected and may temporarily exceed the limits;
source documents and presenter notes are preserved. Changing limits applies at the
next startup; manual expunge remains available immediately.
Since 0.1.68, the unsupported-platform keep-awake protocol test was also corrected.
Linux formatting, warnings-denied Clippy/rustdoc, workspace and native-window tests,
and Python helper tests pass. Whole-application line coverage is **84.46%** against
the 75% floor.
## Packages and preview status
Portable Linux x86_64 and Windows x86_64 bundles, standalone binaries, Cargo binstall
archives and SHA-256 checksums are provided. No Rust toolchain or separately installed
PDF renderer is required at runtime. The Windows executable is unsigned; macOS is
not packaged.
Windows runtime, clean-machine, physical multiscreen, sleep and performance
acceptance remain open. Rehearse on the machines and displays intended for the show;
a successful build or Linux smoke test does not establish those acceptance gates.