deps: bump livetennisapi from 1.4.0 to 1.8.1

[dependabot]

Bumps livetennisapi from 1.4.0 to 1.8.1.

Release notes

Sourced from livetennisapi's releases.

v1.8.1 — native divergence frames

Fix: the native LiveScoreStream silently dropped divergence frames (its dispatch had no case for the type, though the server accepts signals: ['divergence']). They now yield as the typed Divergence added in 1.8.0, and StreamFrame includes Divergence in its union.

v1.8.0 — signals on the push feed

PushStream({signals: true}): break_point / break_point_result / divergence frames now ride the push feed's signal:* channels, subscribed from the /ws-token mint's advertised vocabulary and delivered through the existing async-iterator surface. New Divergence type exported. See CHANGELOG.md.

v1.7.0 — the draw split + the coverage table

Draw type + three-valued Match.draw ('singles' | 'doubles' | null — null is unknown or a team tie, never a guess). draw param on listMatches/listCompletedMatches/listTournaments/listFixtures. New getHistoryCoverage() returns the measured completeness rollup (per tour × draw, as-of dated); 503 coverage_unavailable surfaced as the typed error. Tape blocks gain starts_at_love/computed_at where served. See CHANGELOG.

v1.6.0 — the per-point stream

One record per committed point on every SDK surface, keyed by the per-match gapless seq. REST: getMatchPoints / iterateMatchPoints, covers_from_start on the page. Native streamer: point frames now yielded as PointUpdate instead of being dropped. Push streamer: points: true subscribes the point channels from the mint's vocabulary, pointsResume (default on) REST-catches-up every tracked match on each (re)connect, dedups by seq, fills mid-stream gaps before the trigger frame, and bounds the cursor set (404-prune + 2h idle expiry). RankingSystem gains 'elo' + companion params on listRankings. See CHANGELOG for full detail.

v1.5.0 — PushStream

Built-in push-feed streamer (Centrifugo protocol): PushStream with async-iterator ergonomics mirroring LiveScoreStream, recommended for continuous/production streaming (no shared connection ceiling). Auth-class close codes are fatal (no reconnect loops), dead-connection watchdog on both streamers, strict match-id validation. See CHANGELOG.

v1.4.2 — PackageKind accepts 'archive'

Added

• PackageKind gains 'archive' — the 1968–2022 results archive as yearly bulk packages (bare-year period, same entitlement as the tape packages). The type previously rejected a kind the API accepts.

Changed

• Dev-only: esbuild 0.28.2 (clears a low-severity advisory).

v1.4.1 — the WS score frame is nested; the types now say so

Fixes for the 1.4.0 WebSocket types, verified against the server's frame builders:

• ScoreUpdate typed a frame that never existed. The wire nests the payload: {"type": "score", "match_id": N, "score": {sets, games, points, server, is_tiebreak, timestamp, win_probability_p1, danger}} — model fields inside score. The stream passes the raw frame through, so flat reads (frame.sets) compiled and returned undefined. ScoreUpdate is now {type, match_id, score?: Score}, with a regression test replaying the real nested wire shape verbatim.
• The CLI's watch read the flat fields and printed - for every score — fixed to read frame.score.
• BreakPoint.set / .game are wire strings ('1-1', '3-4'), not numbers — retyped.
• The subscribe frame drops the stray action: 'subscribe' key; it is now exactly the documented {topics, signals?}.

No behavioural change for consumers already reading frame.score; flat-field readers get a compile error pointing at the fix. Full details in CHANGELOG.md.

Changelog

Sourced from livetennisapi's changelog.

[1.8.1] — 2026-08-18

Fixed

• Native LiveScoreStream no longer drops divergence frames. The server accepts signals: ['divergence'] on the native feed, but the stream's dispatch had no case for the frame type and silently discarded every event. Divergence frames now yield (typed Divergence), and StreamFrame includes Divergence in its union.

[1.8.0] — 2026-08-18

Added

• signals: true on PushStream — the signal events, on the push feed. The push feed's signal channels (signal:match:{id} per requested match, or signal:slate) carry the same derived events the native LiveScoreStream delivers through its signals option: break_point (BreakPoint) the moment a break point arises, break_point_result (BreakPointResult) when it resolves, and — where the server's divergence flag is on — divergence (the new Divergence type: model vs match-winner market disagreeing beyond the server's threshold, direction naming the side the model rates above the market). Channel names are resolved from the /ws-token mint's own advertised vocabulary (signal_match / signal_slate), exactly like points: true — an unadvertised vocabulary is the server's honest refusal (the signal feed is off) and throws ServiceUnavailable instead of subscribing a guessed name into a silent empty feed. Signals are events with no replay and no seq: a subscriber that joins mid-break-point does not receive the onset, and there is no resume machinery for them (nothing like pointsResume) — unlike points, a missed signal is not recoverable over REST. Frames arrive through the same iterator, dispatched by frame.type as always.
• Divergence — the new exported frame type; WsToken.channels gains the optional signal_match / signal_slate vocabulary fields.

Changed

• README: PushStream is now the first streaming example. The push feed is the recommended transport for continuous / production streaming; the native /ws feed is documented second, with its shared-capacity ceiling stated. Documentation only — no behavioural change to either streamer.

Notes

• Fully backwards compatible. signals defaults to false; with it omitted PushStream subscribes exactly the channels it did before. Every addition is a new optional option, a new optional field, or a new exported type.

[1.7.0] — 2026-08-18

Added

• draw — singles vs doubles, three-valued and filterable. Match gains draw?: 'singles' | 'doubles' | null (the new Draw type) — and the null

... (truncated)

Commits

• 16537f7 1.8.1: native streamer yields divergence frames instead of silently dropping ...
• ed1c479 1.8.0: signals on the push feed — signal:* channels, vocabulary-first
• 2efe703 types: CoverageBucket.share is null on an empty bucket — the server contract ...
• 331f598 1.7.0: draw + the coverage table — docs and version
• fab67d6 test: draw pass-through + bad_draw, the coverage object, 503-as-answer
• 0953585 client: draw on all four listings + getHistoryCoverage()
• 3567217 types: Draw + Match.draw (3-valued) + the CoveragePage object
• c1699f7 push: bound the resume cursor set — idle matches expire before catch-up
• 083e9ab push: review fixes — a vanished match cannot wedge catch-up; channels deduped
• 96581e7 1.6.0: the live point feed A-Z + Elo rankings — docs and version
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)