Repository navigation
Releases
3.0.2
Fix Specials menu collection when the API advertises a numeric menu ID with isSpecials: true. Requests now use the virtual /menus/specials route, and the response schema accepts its specials ID. This resolves incomplete results caused by HTTP 500/Z556 on the numeric Specials route.
Includes seven regression tests and reference documentation for the official client and API compatibility. The README now provides a short quick start with links to docs/.
Lint, 30 unit tests, and builds passed on Node 22 and Node 24. Targeted live checks returned complete results for Sigered, King of Essex, The Dictum of Kenilworth, Walham Green, The Hykeham Manor, and The Captain Flinders.
The release workflow runs the full all-pub live suite before publishing to npm.
3.0.1
What's Changed
- Gate npm publishing on real API tests by @slack2450 in #1
- Split API unit tests by behavior by @slack2450 in #2
- Harden API workflows by @slack2450 in #3
- Preserve menu failure context for collector diagnostics by @slack2450 in #4
- Release wetherspoons-api 3.0.1 by @slack2450 in #5
Full Changelog: v3.0.0...3.0.1
v3.0.0
Durable request deadlines, retry and cancellation handling, stricter response validation, explicit currency support, and preserved zero-configuration access via Wetherspoons' public client token. Publication is gated by the full live venue suite.