vercel@56.4.1
📦 vercel-functionsView on GitHub →
🐛 4 fixes⚡ 1 deprecations🔧 8 symbols
Summary
This patch release addresses several issues including optional peer dependencies for builders, GET API request flags, launcher loops, and refresh token persistence. It also suppresses a deprecation warning related to `url.parse()`.
🐛 Bug Fixes
- Builders are now declared as optional `peerDependencies`, and their versions are used to pin dynamic Builder installs. Bare specs will install the version this CLI release was published with instead of `latest`. Stale `.vercel/builders` copies are reinstalled. `@vercel/build-utils` is pinned to the CLI's own version. Post-install resolution failures now report a per-Builder reason instead of a generic error message. Explicit Builder version pins remain unchanged and take precedence. Builders are still included in `dependencies`.
- Curl request body flags are no longer emitted for generated GET API requests.
- An infinite launcher loop caused by globally installed `vercel` and `@vercel/vc-native` has been fixed. The launcher will not resolve a native binary when already running inside one (`VERCEL_VC_NATIVE=1`) and will only resolve the native package from its own install tree, ignoring `NODE_PATH`.
- The rotated refresh token is now persisted after the `vc env pull` step-up authentication. This resolves an issue where subsequent step-ups failed with `Device authorization request failed` and eventually forced a re-login due to the old refresh token being kept after a server-side rotation and revocation.
Affected Symbols
⚡ Deprecations
- DEP0169 `url.parse()` deprecation warnings are suppressed in the native binary.