Skip to content

feat: add status-page maintenance command family - #85

Merged
caballeto merged 2 commits into
mainfrom
feat/status-page-maintenance
Aug 23, 2026
Merged

feat: add status-page maintenance command family#85
caballeto merged 2 commits into
mainfrom
feat/status-page-maintenance

Conversation

@caballeto

Copy link
Copy Markdown
Member

Summary

  • Absorb the split incidents/maintenance OpenAPI spec after mono #875.
  • Add devhelm status-pages maintenance (create/list/get/update/delete/publish/dismiss/post-update).
  • status-pages incidents create --scheduled now errors and points at the maintenance command instead of silently creating an incident.
  • Wire new authoring fields (notification-policy description, alert-channel enabled, sms/phone_call configs, DEPENDENCY service) so parity tests stay honest.

Test plan

  • npm test (1056 passing locally)
  • npx tsc --noEmit
  • Create a maintenance window via devhelm status-pages maintenance create against the test API
  • Confirm devhelm status-pages incidents create --scheduled errors with the maintenance pointer

Made with Cursor

caballetoand others added 2 commits August 23, 2026 12:19
Absorb the split incidents/maintenance API and add `status-pages maintenance`
commands. `--scheduled` on incident create now errors instead of silently
creating an incident. Wire new authoring fields (NP description, channel
enabled, sms/phone_call, DEPENDENCY components) instead of hiding them from
parity tests.
Co-authored-by: Cursor <cursoragent@cursor.com>
Locks the new command family and the incident-create migration guard.
Also steers communicate skill copy away from scheduling via incidents.
Co-authored-by: Cursor <cursoragent@cursor.com>
@caballeto
caballeto merged commit 48e7c61 into mainAug 23, 2026
3 checks passed
@caballeto
caballeto deleted the feat/status-page-maintenance branch August 23, 2026 10:39
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@caballeto