Skip to content

chore: sync OpenAPI spec, change_status gains Failed - #84

Merged
ysyneu merged 1 commit into
mainfrom
sync-spec-failed
Sep 29, 2026
Merged

ysyneu merged 1 commit into
mainfrom
sync-spec-failed

Conversation

@ysyneu

@ysyneu ysyneu commented Sep 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

Re-syncs the vendored OpenAPI spec from flashduty-docs and regenerates the models.

  • ChangeItem.change_status and ChangeEventItem.change_status gain the enum value Failed (en + zh spec, doc comment in models_gen.go).
  • No other API changes came with this sync: operation and schema counts are unchanged (37 services, 334 operations, 728 schemas).
  • detail_url on AlertInfo / AlertItem is kept. The upstream spec does not list it yet, so a raw sync would have removed a field that v0.15.6 / v0.15.7 already ship.

Verification

  • make sync-spec output is byte-identical to flashduty-docs main before the detail_url hunks are re-applied.
  • make generate, make test (race), make build pass locally.

Change and change-event items now document a sixth change_status value,
Failed. The vendored spec keeps the detail_url field on AlertInfo and
AlertItem, which the upstream spec does not carry yet.
@ysyneu
ysyneu merged commit 2af2933 into main Sep 29, 2026
4 checks passed
@ysyneu
ysyneu deleted the sync-spec-failed branch September 29, 2026 12:43
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