Skip to content

chore: regenerate schema from upstream spec - #49

Closed
tpw-drift[bot] wants to merge 1 commit into
mainfrom
automated/spec-drift
Closed

tpw-drift[bot] wants to merge 1 commit into
mainfrom
automated/spec-drift

Conversation

@tpw-drift

@tpw-drift tpw-drift Bot commented Sep 25, 2026

Copy link
Copy Markdown

Automated schema regeneration from the api.themeparks.wiki OpenAPI spec.

  • build: success
  • live smoke tests: success

A build failure here means the upstream contract changed in a way
this client cannot absorb automatically. Do not merge until it is
green.

@tpw-drift
tpw-drift Bot force-pushed the automated/spec-drift branch from cbef354 to 4edd768 Compare September 28, 2026 13:59
@cubehouse

Copy link
Copy Markdown
Member

#51 contains this exact schema — git diff between the two branches on src/_generated/schema.ts is empty — plus the code that uses the fields it adds.

This PR had been green and open for three days, and in that time the CSV export in #51's command was silently dropping unknownMinutes, inParkHours and extremeWaits because the vendored types did not have them. The detector did its job; the gap was between it and a merge.

Safe to close once #51 goes in.

@cubehouse

Copy link
Copy Markdown
Member

Superseded by #51, which is merged and carries this exact schema plus the generated column list that goes with it. The nightly job will open a fresh one if the spec moves again.

@cubehouse cubehouse closed this Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant