feat(status-pages): default layout with status banner, paged history and incident calendar by Makisuo · Pull Request #1948 · MapleTechLabs/maple

feat(status): a year of uptime history, an incident calendar index and footer links in the snapshot

Makisuo

committed

69b1b37

feat(status): status page layout with a status banner, paged system status and an incident calendar

Makisuo

committed

9dd1ede

feat(status-pages): privacy_url and terms_url on the v2 API

Makisuo

committed

0c20ff2

feat(web): privacy and terms links in the status page settings, passed to the preview

Makisuo

committed

3b916d1

fix(web): status page URL fields check what the service checks

Makisuo

committed

0f3af5d

fix(status-pages): hero names affected components when no incident is posted; bound the incident index

Makisuo

committed

d7c543e

fix(status-pages): one URL length limit shared by the editor and the service

Makisuo

committed

cd337de

fix(status-pages): open incidents are read uncapped; only resolved ones fill the capped calendar index

Makisuo

committed

308ce50

fix(status-pages): the incident index starts on the first bar day

Makisuo

committed

7b448d4

fix(status-pages): cap resolved incidents by when they resolved, not when they started

Makisuo

committed

5c034f5

perf(status): build the incident calendar in one pass over integer days

Makisuo

committed

79c40bd

chore(status-pages): put the stale-after doc comment back on its constant

Makisuo

committed

2a25673

chore(db): merge the status page footer links migration onto the merged chain

Makisuo

committed

254f8d9

test(status-page): pin the pager's bars, len and end, and the No data uptime span

Makisuo

committed

9c07638

fix(status): the page script floors uptime past float error, matching the server

Makisuo

committed

732224f

Navigation Menu

Repository navigation

feat(status-pages): default layout with status banner, paged history and incident calendar - #1948

feat(status-pages): default layout with status banner, paged history and incident calendar#1948
Makisuo merged 15 commits into
status-pages/7-jsonfrom
status-pages/8-layout

Commits on Oct 31, 2026

feat(status): a year of uptime history, an incident calendar index and footer links in the snapshot

feat(status): status page layout with a status banner, paged system status and an incident calendar

feat(status-pages): privacy_url and terms_url on the v2 API

feat(web): privacy and terms links in the status page settings, passed to the preview

fix(web): status page URL fields check what the service checks

fix(status-pages): hero names affected components when no incident is posted; bound the incident index

fix(status-pages): one URL length limit shared by the editor and the service

fix(status-pages): open incidents are read uncapped; only resolved ones fill the capped calendar index

fix(status-pages): the incident index starts on the first bar day

fix(status-pages): cap resolved incidents by when they resolved, not when they started

perf(status): build the incident calendar in one pass over integer days

chore(status-pages): put the stale-after doc comment back on its constant

chore(db): merge the status page footer links migration onto the merged chain

test(status-page): pin the pager's bars, len and end, and the No data uptime span

fix(status): the page script floors uptime past float error, matching the server