GeezerVison

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 11, 2026 6:51pm

PR Summary

Medium Risk
Touches authenticated usage/rate-limit responses and table group execution defaults; changes restore documented legacy behavior and are covered by focused route/contract tests.

Overview
Restores backward-compatible behavior on three APIs that had regressed, with contracts and tests to keep the shapes stable.

GET /api/users/me/usage-limits again returns the full legacy payload: sync/async rate-limit status (via RateLimiter), usage, and storage, with authType set to api vs manual from hybrid auth. Request validation runs after auth (401 before billing/rate-limit reads). The response is enforced through a strict usageLimitsResponseSchema instead of a loose passthrough contract.

POST /api/table/[tableId]/groups maps autoRun with body.autoRun ?? true, so omitted autoRun keeps the legacy default of auto-run while autoRun: false still opts out.

Public workflow log pagination accepts legacy cursors that only contain startedAt and id by treating missing order as the caller’s expectedOrder, instead of rejecting them.

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

Greptile Summary

Restores three legacy API behaviors without changing their established authentication boundaries.

• Restores rate-limit details in the usage-limits response and validates the complete response contract.
• Preserves the first-party table-group auto-run default while honoring explicit opt-out.
• Allows pre-order-binding log cursors to continue under the requested order.
• Adds focused route, contract, and cursor compatibility tests.

Confidence Score: 5/5

The PR appears safe to merge, with no actionable changed-code defects identified.

The restored defaults and response fields match established legacy contracts, rate-limit status retrieval fails softly, explicit modern cursor order binding remains enforced, and focused tests cover the compatibility paths.

_{Reviews (1): Last reviewed commit: "fix(api): restore legacy endpoint compat..." | Re-trigger Greptile}