Releases: arrsome/softarr
Releases · arrsome/softarr
Softarr v1.0.1
Bug fixes in v1.0.1
TOTP / 2FA fixes (e928379, f1e61c8)
- Fixed a bug where re-visiting the 2FA setup page would overwrite an already-enrolled secret, causing "Invalid code" errors
- TOTP setup now reuses the pending secret on subsequent visits instead of regenerating it
- Increased TOTP clock skew tolerance from ±30s to ±60s to reduce failed logins on devices with slightly drifted clocks
- Fixed TOTP reset flow -- resetting 2FA now correctly clears the enrolled secret and allows fresh enrolment
- Added integration and unit test coverage for the full TOTP enrolment lifecycle
SABnzbd error handling (f1e61c8)
- Fixed SABnzbdError exception handling in the actions API to surface connection errors properly rather than swallowing them
System health page -- version check (2e363c2)
- Fixed the SECURITY section incorrectly reporting the running version as v1.3.18 (an old test/dev version that had crept into pyproject.toml)
- Fixed the version comparison using string equality (==) -- it now uses semantic version comparison so "up to date" correctly means running >= latest GitHub release
1.0.0
Softarr v1.0.0
Initial stable release of Softarr, a software-focused ARR-style release manager built for controlled, visible, and safer handling of software downloads.
This release introduces the core workflow and platform foundations:
- Release discovery across GitHub, Newznab, and Torznab sources
- Structured workflow: discovered -> staged -> reviewed -> approved -> downloaded
- Security analysis including signature verification, archive inspection, and hash intelligence
- Trust and flag system with clear risk visibility
- Integration with SABnzbd and qBittorrent
- Role-based access control with TOTP 2FA
- Observability with metrics, structured logging, and audit logs
- Clean, responsive UI with a focus on usability
Softarr does not automatically download or install anything. All actions require explicit review and approval.
This release is production-capable but still evolving. Feedback, issues, and contributions are welcome via GitHub.