You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(webapp): one reader for Vercel project env vars
The project env endpoint returns every record in one response: no `limit`
parameter, no cursor. Only the team-level shared endpoint pages, and that read
already walks its cursor. Measured against a project holding 500 records.
The call sites had drifted to three different answers about that. One warned
that variables might be missing, one refused to act on a list it believed
truncated, and five said nothing at all. The warning fired on nothing and read
like a known limitation, which is how it came to be believed.
Project env reads now go through readProjectEnvs, which extracts the records and,
if Vercel ever does add a cursor here, logs that the read is silently partial
instead of implying a cap that does not exist.
"Vercel project env list returned a pagination cursor — this endpoint has always returned every record in one response, so this read is incomplete and needs paginating",
0 commit comments