vercel@54.21.0
📦 vercel-functionsView on GitHub →
✨ 4 features🐛 6 fixes🔧 6 symbols
Summary
This release enables monorepo subdirectory build fixes by default, improving dependency handling in linked projects. It also introduces opt-in framework detection during builds and adds a command to update project settings.
Migration Steps
- To restore the previous behavior regarding monorepo subdirectory build fixes, pin an earlier CLI version.
✨ New Features
- Monorepo subdirectory build fixes are now enabled by default, scoped to directories claimed by the workspace.
- When building from a linked project directory, the build now re-anchors to the workspace root, expressing the project path relative to the root, ensuring correct builder tracing, packaged hoisted dependencies, and preserved symlinks in standalone output.
- Framework detection during `vc build` is now opt-in via `VERCEL_FRAMEWORK_DETECTION=1`, recording the detected framework on first deployment (`VERCEL_FIRST_DEPLOYMENT=1`) and validating the build output.
- Added a project update command for changing framework and build settings.
🐛 Bug Fixes
- Global flags (e.g. `--scope`) are no longer duplicated in agent-output `next[]` command suggestions when the command template already contains the flag.
- Projects for `domains inspect` and `domains rm` are now resolved from the domain's project-domains instead of scanning every project in the account.
- Show list help instead of transfer-in help for `vercel domains ls --help`.
- Skipped installation of agent skills if the link is non-GitHub or unparseable during `integration add`.
- Emit structured agent-output JSON (`project_not_found` with runnable `next` suggestions) when `vercel list <project>` does not resolve in non-interactive mode.
- Ignored redundant `rootDirectory` settings that pointed to a folder that already existed at the link location, emitting a warning instead of crashing.