Lataa Vitals 1.0.2

Changed
- Android: two builds. The Google Play build no longer asks for access to all
files, which Google refused for a system monitor. Its storage screen shows
what fills the phone or TV by category, which apps keep the most cache, and
opens the system's storage manager for the rest. The APK on GitHub keeps
the full folder scan and file cleanup.
Fixed
- Google Play: the release workflow now refuses a Play bundle that declares
all-files access, so the rejection cannot recur unnoticed.
Downloads
──────────────────┬───────────────────────────
Windows │Installer
──────────────────┼───────────────────────────
Intel / AMD (x64) │Vitals_x64-setup.exe
──────────────────┼───────────────────────────
ARM64 (Snapdragon)│Vitals_arm64-setup.exe
──────────────────┴───────────────────────────
Verifying this download
Windows may show a SmartScreen warning on first run (Windows protected your
PC) because the installer is not yet signed with a commercial certificate.
Choose More info → Run anyway. That is expected — see
docs/distribution.md.
You do not have to take our word for what is in the binary. With the
GitHub CLI:
gh attestation verify .\Vitals_x64-setup.exe --repo dragoscv/vitals
This proves the file was built by this repository's release workflow from the
tagged commit, and nowhere else. Checksums for every file are in
SHA256SUMS.txt:
(Get-FileHash .\Vitals_x64-setup.exe -Algorithm SHA256).Hash.ToLower()
Software bills of materials (CycloneDX) for the Rust and JavaScript
dependencies are attached as sbom-rust.cdx.json and sbom-js.cdx.json.
Full Changelog: v1.0.1...v1.0.2