Skip to content

momputer 0.3.2

Choose a tag to compare

@github-actions github-actions released this 14 Oct 15:06

NVIDIA and Steam cache groups

  • NVIDIA shader caches group by application when local cache metadata identifies the owner. Unknown entries remain explicitly unknown.
  • Steam shader caches show game names from local manifests across Steam libraries. A missing manifest is described as missing installation information, not proof that a game was uninstalled.
  • NVIDIA installer and download caches are labelled as cached packages rather than installed driver versions.
  • The widget can now delete explicitly selected NVIDIA and Steam shader files through a dedicated, restricted operation. Other cleanup remains temporarily unavailable.

The shader operation works from a fresh, single-use scan. It rechecks file identity and modification metadata, honours kept paths, skips linked/read-only/busy/inaccessible files and does not elevate or change permissions. A completed or failed attempt consumes its selection; another scan is required before trying again. No real user cache was deleted during validation.

Shader deletion is permanent. Folders are left in place, and games may regenerate cleared shaders with temporary stuttering. The operation does not establish that an application is idle or uninstalled.

Browser/session data, duplicate removal, Room Apply/Undo, archive operations, installer deletion, AMD/Intel/DirectX cleanup and general CLI cleanup remain held. The 0.3.1 browser-card and selection fixes remain included.

Build provenance

Built from 0d0fe71163b1206c2fc2c192c77a91d2cd400b46, based on the published 0.3.1 commit. Third-party Cargo dependencies and release compiler settings are unchanged.

CI results · Release build. Installer checksums are included in SHA256SUMS.txt.

Validation

  • GitHub CI passed 237 native tests (235 core and 2 CLI), including all 14 shader-cleanup fixture tests; 3 existing tests remain ignored. All 36 UI regression tests passed.
  • The exact GitHub NSIS and MSI downloads, both embedded GUI/CLI copies, and executable installer helpers completed 12 individual Microsoft Defender scans on 14 October 2026 with intelligence 1.461.18.0. Antivirus, real-time protection, behaviour monitoring and IOAV protection were enabled before and after the scans. No new detections or adverse events were observed during that validation window.
  • Scan-start and scan-completion events were matched by scan ID and exact artifact path. All artifact SHA-256 hashes remained unchanged, and the NSIS/MSI GUI and CLI payloads matched byte for byte. Both application binaries report version 0.3.2.

These were non-elevated scans. Exact exclusion coverage was not probed; the recorded policy and scan events were inspected separately. The results describe these bytes under the recorded Defender definitions, not a guarantee about future detections. A local smoke test of the packaged application has not been completed; automated functional validation is the CI testing described above.

The release is unsigned. An unknown-publisher notice and an antivirus threat detection are different; do not bypass antivirus detections or restore quarantined files.

A separate local debug test binary was flagged by Defender and was not executed. It is not included in the installers, and that detection remains unresolved. This release does not claim that this or earlier candidate detections were confirmed false positives.