# SDKs 0.26.1 stop at the last page (https://docs.predictorsdk.com/changelog/2026-10-20-sdk-0-26-1)

2026-10-20 · SDK, Fix

In the Python and TypeScript SDKs, asking for the page after the last one no longer starts over from the first page. Nothing else changed shape.

The TypeScript (`@predictorsdk/client`), Python (`predictorsdk`), and Go (`github.com/PredictorSDK/sdk-go`) SDKs are released at 0.26.1.

- **Python: `next_page()` returns `None` after the last page.** It used to fetch the first page again, so a loop such as `while page: ...; page = page.next_page()` never ended. Iterating a pager, `iter_pages()` and `has_next` were always right.
- **TypeScript: `getNextPage()` throws after the last page** instead of replacing it with the first page. Check `hasNextPage()` first; iterating with `for await` was always right.
- **Go** already returned `core.ErrNoPages` after the last page and is unchanged.
- **Descriptions.** Docstrings picked up wording from the API reference since 0.26.0 (Polymarket Protocol V2 markets, ProphetX coverage, Hyperliquid lookups).

Nothing in a request or response changed shape, so nothing is breaking. We checked each published package against the production API: walking NFL matched games 20 at a time, Python's `next_page()` (sync and async) stopped after the second and last page, TypeScript's `getNextPage()` threw there and kept the last page, and Go's `GetNextPage` ended with `core.ErrNoPages`.