ReproCrate v0.6.1 (CLI and Desktop maintenance pre-release)

ReproCrate v0.6.1 — privacy and history maintenance pre-release

Experimental maintenance release; not stable v1.0.0. Release publication is gated on validated Rust CLI and native desktop builds on Linux, Windows and macOS. Packages are unsigned developer-preview archives with SHA-256 files, not installers.

This patch preserves CLI compatibility and report schema 1.0.0. It adds no automatic uploads, filesystem scanning, recipe execution, account features or network integrations.

Fixes

• Safer reviewed-report exports: on Unix, newly created reviewed JSON files request owner-only 0600 permissions, independent of a permissive process umask. Exports continue to refuse overwrite and delete a failed partial write.
• Safer desktop file imports: the native reader verifies the opened handle is a regular file; on Unix it additionally compares the originally selected file's inode and device with the opened handle to reject common path-swap races.
• History database schema protection: an existing SQLite database with an unsupported future user_version is rejected rather than silently reset to v1.
• Stable history paths: explicitly indexed report paths are canonicalized after report validation, avoiding duplicate entries for equivalent relative paths and entries tied to a process working directory.
• Regression coverage: protect review no-overwrite and Unix permissions, and ensure that higher-version history databases remain unchanged.

Privacy and limitations

Manual review remains essential. Exports may include sensitive data that generic redaction does not detect; paths and history metadata may also be private. Owner-only mode applies to Unix only; Windows access control depends on local system settings. Checking the opened file does not eliminate every concurrent filesystem race. SQLite deletion cannot guarantee removal from backups or snapshots. A command intentionally captured by the CLI is not sandboxed.

Distribution

The gated v0.6.1 workflow is expected to create three genuine unsigned CLI archives and three genuine unsigned desktop archives, one of each for Linux x86-64, Windows x86-64, and macOS ARM64, plus individual SHA-256 checksums. Publication must not be claimed until the workflow passes and the GitHub Releases API confirms the assets.

See security boundaries, history guide, desktop guide, and change handoff.