vercel@54.1.0
📦 vercel-functionsView on GitHub →
✨ 6 features🐛 4 fixes🔧 8 symbols
Summary
This release renames the `vercel connex` command to `vercel connect`, enables it by default, and introduces new attachment and trigger management features for Vercel connectors. Significant improvements were also made to the CLI setup and deployment output formatting for better visual consistency.
Migration Steps
- If you were using the internal `FF_CONNEX_ENABLED` flag to access connector functionality, you no longer need it; the functionality is now enabled by default.
- If you relied on the legacy `/~/connex/` dashboard route, update links as it now redirects from `/~/connex/` to `/~/connect/`.
✨ New Features
- Added `vercel connect detach` command to detach a Vercel project from a connector via a DELETE API call.
- Added `--triggers`, `--trigger-branch`, and `--trigger-path` flags to `vercel connect attach` to register the project as a trigger destination.
- Enabled `vercel connect` command by default, marking it as beta in `--help` output.
- Introduced `preDeployCommand` support for experimentalServices.
- Added a new aligned-label output format for status rows in `vc deploy` and `vc redeploy` output.
- Added a terminal `✓ Ready in Xs` line at deploy completion.
🐛 Bug Fixes
- Fixed `vercel connect open` to link directly to the renamed `/~/connect/` dashboard route, removing reliance on the legacy redirect.
- Fixed setup flow crash when no services were detected by using optional chaining on `detectServicesResult.resolved?.source`.
- Skipped redundant deploy project and final deployment fetches in the CLI success path.
- Reduced CLI startup bundle size by lazy-loading error reporting and extension execution paths.