# Changelog of Status Page Monitor - StatusLedger (`leons0016/status-page-monitor-ledger`) Actor

- **URL**: https://apify.com/leons0016/status-page-monitor-ledger/changelog.md
- **Full Actor documentation**: https://apify.com/leons0016/status-page-monitor-ledger.md

## Changelog

### 1.0.2 (31 October 2026)

- Fix: the run-summary row listed `warnings` as an object but the dataset schema said array, so the platform rejected the push ("Schema validation failed"); the schema now allows both. A test validates every pushed row against the dataset schema.
- README: narrow-coverage section and non-affiliation line at the top.

### 1.0 (30 October 2026)

First release.

- Reads Atlassian Statuspage (public v2 JSON, or the robots-permitted index.json, history.atom and history.json when robots.txt disallows /api/), Instatus (v3 summary, components and history.atom) and status.io (public status API).
- Full incident timelines with every update, kept in an append-only ledger (named key-value store) that survives between runs; changes of severity and end time are kept in the incident history.
- Incidents and components are kept apart; optional component rows for components that are not operational or changed.
- Monthly uptime and SLA-credit report per vendor (previous month, automatic, month to date), downtime basis and credit tiers configurable, credit in dollars from an optional monthly fee.
- One row per status page in every run (ok, failed or unsupported, with an explanation); no cap on results per run.
- Pay per event: vendor-checked (primary), incident-recorded, monthly-sla-report. Free plan: 5 status pages per run.