GeezerVison

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 12, 2026 2:20am

PR Summary

Medium Risk
Changes default pagination behavior for table row APIs (short pages by byte budget) and switches list-rows cursor encoding, which can break clients that stop on page fullness or expect offset-based cursors.

Overview
Bounded row pages now default to a 5MB byte budget, so list/query responses may return fewer rows than the requested limit. Clients must keep paging until nextCursor is null. TABLE_MAX_PAGE_BYTES remains overridable.

v2 GET /tables/{tableId}/rows now passes opaque native keyset cursors through instead of encoding/decoding offset cursors. Malformed cursors are rejected, and OpenAPI docs call out the short-page behavior.

^{Reviewed by Cursor Bugbot for commit d0d3a42. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

The PR changes v2 table-row listing to pass native storage cursors through the API and enables a default 5MB cap for bounded row pages.

• Moves cursor decoding and validation into the authorized table-row application use case.
• Returns the native nextCursor produced by row storage pagination.
• Defaults bounded row pages to a configurable 5MB byte budget.
• Updates tests, API contracts, and OpenAPI documentation for short-page behavior.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

_{Reviews (2): Last reviewed commit: "fix(tables): cap row pages and use nativ..." | Re-trigger Greptile}

@greptile

@cursor review