UnpackUI v1.8.0

UnpackUI v1.8.0: Per-App Safety Controls

UnpackUI v1.8.0 incorporates the latest upstream extraction-safety and platform-versioning work while retaining UnpackUI's status dashboard, API, webhook notifications, watched-folder recovery, and archive-completeness protections.

Per-app archive safety

• Starr applications now use workload-specific byte caps by default: Sonarr and Whisparr 20 GB, Radarr 75 GB, Lidarr 4 GB, and Readarr 1 GB.
• Starr jobs default to 1,000 extracted entries, a 5:1 expansion ratio, 8 nested archives, and extras depth 3.
• Each Starr instance may override max_bytes; 0 or 0B makes that instance unlimited.
• Watched folders remain unlimited by default and now support optional max_bytes, max_files, max_ratio, max_nested, extras_max_depth, and allow_symlinks settings.

Retry and failure handling

• max_retries = 0 now resolves to the safe default of 2 retries instead of retrying indefinitely.
• Extraction-limit failures do not retry.
• Starr jobs that exhaust retries remain visible as EXTRACTFAILED instead of being promoted to DELETED.

Platform builds and maintenance

• Windows executables now receive FileVersion metadata from the release version.
• macOS CFBundleShortVersionString is stamped from the release version.
• Updated xtractr and supporting dependencies.
• CI now follows the fork's web-ui default branch.

Upgrade note

The global max_bytes, max_files, and max_ratio settings from v1.7.0 are replaced by the per-app and per-folder behavior above. Review custom limits when upgrading, especially if legitimate Sonarr, Lidarr, Readarr, or Whisparr archives exceed the new defaults.

Verification

• go generate ./...
• go test ./...
• golangci-lint run ./...
• Hosted Go tests and lint passed on Linux, FreeBSD, and Darwin.