MokoConsulting/MokoSuiteBackup

fix: use warning status when backup succeeds but upload fails #199

Merged

jmiller merged 4 commits from fix/upload-fail-warning-status into main

2026-06-30 19:18:07 +00:00

Author	SHA1	Message	Date
gitea-actions[bot]	9820d75212	chore(version): pre-release bump to 02.52.24-dev [skip ci] Universal: Build & Release / Promote to RC (pull_request) Has been skipped Details RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped Details Branch Cleanup / Delete merged branch (pull_request) Successful in 1s Details Universal: Build & Release / Build & Release Pipeline (pull_request) Successful in 24s Details Universal: Workflow Sync Trigger / Sync workflows to live repos (pull_request) Successful in 2m56s Details	2026-06-30 19:17:57 +00:00
jmiller	9c0c6eae15	docs: add warning status changes to changelog Universal: PR Check / Branch Policy (pull_request) Failing after 2s Details Joomla: Extension CI / Lint & Validate (pull_request) Failing after 6s Details Generic: Repo Health / Access control (pull_request) Successful in 2s Details Generic: Repo Health / Site Health (pull_request) Has been skipped Details Joomla: Extension CI / Release Readiness Check (pull_request) Failing after 6s Details Universal: PR Check / Validate PR (pull_request) Failing after 7s Details Universal: PR Check / Secret Scan (pull_request) Successful in 10s Details Generic: Project CI / Lint & Validate (pull_request) Successful in 16s Details Universal: Pre-Release / Build Pre-Release (${{ inputs.stability \|\| github.ref_name }}) (push) Successful in 23s Details Universal: Build & Release / Promote to RC (pull_request) Has been skipped Details Universal: Build & Release / Build & Release Pipeline (pull_request) Has been skipped Details Joomla: Metadata Validation / Validate Joomla Metadata (pull_request) Successful in 36s Details Generic: Project CI / Tests (pull_request) Has been cancelled Details Joomla: Extension CI / Tests (PHP 8.2) (pull_request) Has been cancelled Details Joomla: Extension CI / Tests (PHP 8.3) (pull_request) Has been cancelled Details Joomla: Extension CI / PHPStan Analysis (pull_request) Has been cancelled Details Joomla: Extension CI / Build RC Pre-Release (pull_request) Has been cancelled Details Universal: PR Check / Build RC Package (pull_request) Has been cancelled Details Universal: PR Check / Report Issues (pull_request) Has been cancelled Details Generic: Repo Health / Scripts governance (pull_request) Has been cancelled Details Generic: Repo Health / Repository health (pull_request) Has been cancelled Details Generic: Repo Health / Report: Scripts Governance (pull_request) Has been cancelled Details Generic: Repo Health / Report: Repository Health (pull_request) Has been cancelled Details Claude-Session: https://claude.ai/code/session_01MbEjBtsSjPuTWhqqrMS2wG	2026-06-30 14:17:34 -05:00
gitea-actions[bot]	1daa6869cc	chore(version): pre-release bump to 02.52.23-dev [skip ci]	2026-06-30 19:14:33 +00:00
jmiller	aefa46e0c4	fix: use warning status when backup succeeds but remote upload fails Universal: Pre-Release / Build Pre-Release (${{ inputs.stability \|\| github.ref_name }}) (push) Successful in 19s Details Previously a successful backup with a failed remote upload was marked as "complete", hiding the upload failure. Now these records get a "warning" status with a yellow badge so operators can see at a glance which backups didn't reach their remote destination. Warning-status records are treated as usable backups throughout: - Downloadable, browsable, and restorable (the archive is intact) - Counted in dashboard stats, storage totals, and success streaks - Included in purge operations and differential base lookups - Shown with yellow "warning" badge in list, detail, and cpanel module - Filterable via the status dropdown on Backup Records Claude-Session: https://claude.ai/code/session_01MbEjBtsSjPuTWhqqrMS2wG	2026-06-30 14:14:06 -05:00