Gitpulse
LatestReleasesStand-up
Merged
Size
L
Large: 500-1000 weighted lines
Change Breakdown
Bug Fix50%
Feature30%
Refactor20%
#3149feat(vercel): Vercel SDK fixes and correct env vars behavior for staging envs

Vercel SDK schema validation errors bypassed for reliable environment syncing

0S
0ski
·Feb 28, 2026·#3149feat(vercel): Vercel SDK fixes and correct env vars behavior for staging envs

A recovery mechanism bypasses strict Vercel SDK schema validation errors, fixing environment variable synchronization for staging and production deployments.

Environment variables are synced to Vercel, particularly for staging environments, bypassing strict SDK validation constraints.

A recovery mechanism handles cases where Vercel's API returns valid data that slightly mismatches expected types, such as returning a null value instead of a number. are intercepted, the raw JSON response is extracted, and only the required fields are re-validated using permissive .

Authentication keys are synced to the correct when project settings are updated. The integration settings interface features updated toggles for discovering and pulling environment variables before builds.

View Original GitHub DescriptionFact Check
Fact Check Notice: The PR changelog focuses entirely on the internal Vercel SDK recovery wrappers, but omits the significant logic added for synchronizing the TRIGGER_SECRET_KEY across Vercel custom environments (`syncStagingKeyForCustomEnvironment`) and the corresponding UI updates to the Build Settings page.

✅ Checklist

  • I have followed every step in the contributing guide
  • The PR title follows the convention.
  • I ran and tested the code works

Testing

Vercel onboarding

Changelog

  • Import callVercelWithRecovery, wrapVercelCallWithRecovery and VercelSchemas and plug them into vercelIntegration flows.
  • Use wrapVercelCallWithRecovery for team/user lookups, project env listings, environment variable listings and shared env endpoints so responses are validated and errors are converted consistently.
  • Replace several ResultAsync.fromPromise usages with callVercelWithRecovery to attach schema checks and contextual metadata (e.g. validateVercelToken, resolveEnvVarValue).
  • Thread through toVercelApiError where appropriate to normalize error mapping.

Screenshots

💯

© 2026 · via Gitpulse