Rich text annotation types exported; pagination helpers fixed under strictNullChecks
v5.23.1
2 fixesThis release2 fixesBug fixesAI-tallied from the release notes
From the original release noteView original ↗
What's Changed
Type & bug fixes
-
Rich text annotation types are now exported (#740)
- Adds
ApiColor,RichTextItemResponseCommon, and a newAnnotationResponsealias (the type ofRichTextItemResponse.annotations) to the package entrypoint. Fixes #689; thanks @KingJing1. - If you validate or construct rich text annotations: import these types directly instead of deriving them from
RichTextItemResponsewith indexed-access types.
- Adds
-
Pagination helpers accept endpoint methods again under
strictNullChecks(#744)- v5.23.0 widened endpoint params to
start_cursor?: string | null, but thePaginatedArgsconstraint used byiteratePaginatedAPI/collectPaginatedAPIstill only allowedstring— so passing methods likeclient.dataSources.queryto the helpers stopped compiling, with a misleading "property missing in typePaginatedArgs" error. Types-only fix (the runtime already handlednullcursors), plus a regression test that compiles a real endpoint method against the helpers so this can't silently regress again. Fixes #743; thanks @nakanoasaservice. - If the pagination helpers broke for you on v5.23.0, this is the fix — no code changes needed on your side.
- v5.23.0 widened endpoint params to
-
Doc-comment fix:
updateDataSourceicon/in_trashdescriptions now reference data sources (#745)- Generated documentation strings only; no type or runtime changes.
-
Bump version to v5.23.1 (#746)
New Contributors
- @KingJing1 made their first contribution in #740
- @nakanoasaservice made their first contribution in #744
Links
Fetched July 15, 2026


