Releases: NichlasB/alynt-drime-backups-dashboard
Release list
Alynt Drime Backups Dashboard 0.1.17
Patch release for V2.2 action-history reconciliation. Fixes newly dispatched Request Backup Now rows so the dashboard stores the signed action UUID as the action record public ID, matching the client-reported remote_actions.last_action.action_id. No new remote powers are added; the action boundary remains limited to separately opted-in scan_upload_now.
Alynt Drime Backups Dashboard 0.1.16
V2.2 dashboard-side action-history reconciliation and audit hardening. Adds additive client action report storage, stale-action reconciliation after successful status polls, clearer Site Detail action-history evidence, compact Sites-row latest-client-action hints, and Diagnostics aggregate action counts. This release preserves the existing safety boundary: no restore, delete, cleanup, schedule-management, credential, Drime-token, or arbitrary-command powers.
Alynt Drime Backups Dashboard 0.1.15
What's New in v0.1.15
This release adds the dashboard-side V2.1 Request Backup Now dispatcher and action history while keeping dashboard monitoring read-only unless each client site separately opts into signed action requests.
Highlights
- Adds Request Backup Now dispatch for the bounded scan/upload-now action.
- Adds V2.1 action opt-in readiness, signed dispatch, and fail-closed response validation.
- Adds bounded, redacted action-history storage/display and schema cleanup hardening.
- Keeps the dashboard free of Drime credentials and higher-risk restore/delete/cleanup/settings actions.
Upgrade Notes
No breaking changes. The dashboard schema upgrades to version 6 for the action-history table/index; live deployment should be preceded by a restore point.
Alynt Drime Backups Dashboard 0.1.14
Fixed\n\n- Hardened uninstall safety so WordPress-discovered rollback copies exit before touching canonical dashboard state.\n- Preserved dashboard records by default during normal canonical plugin deletion.\n- Required the explicit ALYNT_DRIME_BACKUPS_DASHBOARD_PURGE_DATA_ON_UNINSTALL wp-config.php constant for permanent dashboard-data removal.\n- Documented safe rollback archive placement outside wp-content/plugins.\n\nThis remains a read-only dashboard patch; it adds no remote actions.
Alynt Drime Backups Dashboard 0.1.13
Added
- Added an always-on, bounded, redacted operator action history for dashboard-local actions such as pairing-token creation, local revocation, manual Check Now, and diagnostics changes.
Validation
- CI passed on PHP 7.4 and 8.3.
- Local validation passed: npm.cmd test, npm.cmd run lint, npm.cmd run build, Composer validate/audit, npm audit, PHP syntax sweep, and git diff --check.
Alynt Drime Backups Dashboard 0.1.12
Allows dashboard ingestion of WPvivid Pro/addon schedule policy basis labels reported by live uploader sites.
Alynt Drime Backups Dashboard 0.1.11
Consumes uploader-reported WPvivid schedule policy summaries for schedule-aware Sites/detail freshness display while preserving the v1 read-only boundary.
Alynt Drime Backups Dashboard 0.1.10
Added
- Added a dashboard-side WPvivid freshness policy so weekly or biweekly WPvivid backup evidence can remain healthy while server-runner evidence stays strictly monitored.
- Sites/detail backup-source evidence now shows Within policy and expected freshness windows such as within 15 days.
Validation
- CI passed on PHP 7.4 and PHP 8.3 for commit bbc6cfde35b82cc985079adf7b7c5cfdac8ff677.
- Local validation passed: npm.cmd test, npm.cmd run lint, npm.cmd run build, and git diff --check.
Read-only dashboard boundary preserved: no remote backup, restore, delete, cleanup, settings, credential, Drime token, or arbitrary command actions.
Alynt Drime Backups Dashboard 0.1.9
Fixed
- Aligned the Sites-tab helper copy with the shortened Check Now manual status-check button label.
Validation
- CI passed on PHP 7.4 and PHP 8.3 for commit abfc5d03b8f6152640f5dc56480a96f9dafbe96a.
- Local validation passed: npm.cmd run build, npm.cmd run lint, npm.cmd test -- --filter AdminPagePollingStateRenderingTest, and git diff --check.
Read-only dashboard boundary preserved: no remote backup, restore, delete, cleanup, settings, credential, Drime token, or arbitrary command actions.
Alynt Drime Backups Dashboard 0.1.8
What's New in v0.1.8
This patch release completes the post-0.1.7 local hardening pass and records the next-version remote-action planning boundary. The dashboard remains read-only: it does not add remote backup, restore, delete, cleanup, settings, credential, Drime-token, or arbitrary command actions.
Highlights
- Added accessible busy-state feedback for pairing-token, diagnostics-event, and support-summary copy buttons.
- Added timestamp fallback hardening for WordPress admin date/time format reads.
- Treated malformed or empty stored status snapshot payloads as not reporting instead of falling through to a misleading configuration state.
- Added v2 remote-action planning documentation while preserving the v1 read-only contract.
Changelog
Changed
- Added accessible busy-state feedback for pairing-token, diagnostics-event, and support-summary copy buttons.
- Added explicit WordPress date/time format fallbacks for admin timestamp rendering.
- Added v2 remote-action planning documentation while preserving the v1 read-only boundary.
Fixed
- Treated malformed or empty stored status snapshot payloads as not reporting instead of falling through to a misleading configuration state.
Tests
- Added focused status-classifier regression coverage for malformed JSON and empty decoded snapshot payloads.
Upgrade Notes
No breaking changes in this release.