Skip to content

fix(api): regen for unified ComponentUptimeDayDto#9

Merged
caballeto merged 1 commit into
mainfrom
fix/unify-uptime-day-dto
Apr 23, 2026
Merged

fix(api): regen for unified ComponentUptimeDayDto#9
caballeto merged 1 commit into
mainfrom
fix/unify-uptime-day-dto

Conversation

@caballeto
Copy link
Copy Markdown
Member

Summary

Spec resync following mono PR devhelmhq/mono#269, which collapses the catalog and status-page ComponentUptimeDayDto shapes into a single canonical type.

mcp-server has no codegen of its own — types come from the upstream devhelm SDK, which is being re-released in devhelmhq/sdk-python#8.

What changed

  • docs/openapi/monitoring-api.json resync'd from mono (used by parity + spec-check workflows).
  • uv.lock refreshed after SDK relink — also catches up the package's own already-bumped 0.3.0 version.

No source code changes.

Tests

  • make lint → clean (ruff check + format)
  • make typecheck → mypy strict, no issues
  • make test57/57 pass

Test plan

Made with Cursor

Mono PR devhelmhq/mono#269 collapses the catalog/status-page DTOs into a
single canonical `ComponentUptimeDayDto` (typed `incidents[]` +
`degradedSeconds`; `eventsJson`/`source` gone, `StatusPageComponentUptimeDayDto`
removed). The vendored OpenAPI spec is resync'd; the SDK relink during
`scripts/regen-from.sh` also surfaced a stale uv.lock entry for the
already-bumped 0.3.0 package version.

57/57 pytests pass; mypy + ruff clean.

Made-with: Cursor
@caballeto caballeto merged commit 68a44e1 into main Apr 23, 2026
4 checks passed
@caballeto caballeto deleted the fix/unify-uptime-day-dto branch April 23, 2026 16:58
Sign up for free to 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