release: v8.0.0 - #39
Merged
Merged
Conversation
Ships the corrected schema, regenerated after the upstream spec stopped describing a park's schedule two different ways. The headline fix is that schedule entries expose `purchases` and a `type` union again. The spec described the nested-under-a-destination path precisely and the direct path loosely, and the direct path is the one this client uses, so 27 Magic Kingdom entries carrying purchases were invisible without a cast. `purchases[].price.amount` is also nullable now, matching PriceData — 7.1.0 fixed one copy of the price shape and there was a second, inline one. Breaking for strict TypeScript consumers in three places, each documented in the changelog: `tags[].value` becomes `unknown` because the spec declares no type for it, `location` and `purchases[].type` lose a `| null` the API never sends, and the Node floor moves to 20. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump and changelog for 8.0.0. Tagging
v8.0.0after this merges publishes to npm.What ships
Regenerated schema, after the upstream spec stopped describing a park's schedule two different ways.
Fixed
purchases, andtypeis a union again. The direct schedule path — the one this client uses — was described loosely upstream while the nested path was precise. Magic Kingdom serves 27 entries carrying purchases that were previously unreachable without a cast.purchases[].price.amountis nullable, matchingPriceData. 7.1.0 fixed one copy of the price shape; a second inline copy keptamountnon-nullable. Tokyo Disneyland serves six Premier Access rows with a null amount.descriptionfield the API has always sent.Breaking, each with a migration note in the changelog:
tags[].valueis nowunknown— the spec declares no type for it, so the old union was an inventionlocationandpurchases[].typelose| null, verified against 412 children and 255 purchases in productionVerification
npm ci, typecheck, lint, 64 unit tests, build and 4 live smoke tests all pass on this branch. Prettier clean.🤖 Generated with Claude Code