Node Version and Deployment Handling
Newly created Deployments now run Node.js 12.18.3, up from 12.16.2. Existing code requires no changes; simply create a new Deployment to pick up the newer runtime. The RedwoodJS framework is now auto-detected when you create a Project through the Dashboard or Vercel CLI. A redeploy or promotion to Production now uses an updated pipeline that meaningfully improves reliability for those operations.
If you upload a custom SSL Certificate, it now takes precedence over system-generated certificates. Errors that occur when a Runtime fails to install from npm during the Build Step will now surface in the build logs. For new Projects, choosing "Other" as the framework preset no longer triggers Next.js auto-detection; existing Projects are unaffected. When a vercel-build script exists in package.json, it is now preferred over a standard build script.
Dashboard Refinements
The "Visit" button on the Deployment View always links to the Deployment's own URL, regardless of any other assigned Domains. Each Project on the Dashboard now includes an "Updated" indicator showing when settings last changed and when the most recent Deployment was created.
The Production Deployment card now uses a deterministic method to pick the "Primary Domain." Starting with Domains in Project Settings, it selects one with neither a Redirect nor a Git Branch, preferring the shortest name alphabetically. The "Visit" button on the Project View follows the same logic. The card also now previews the upcoming Deployment that will become your next Production Deployment.
RedwoodJS is selectable as a framework preset in Project Settings. The Logs and Source Protection toggle now also applies to Deployments created before July 9th, 2020 at 7:05 AM (UTC), which previously were excluded. Screenshots will no longer accidentally capture a login screen.
Creating a Project from a public GitLab repository no longer requires linking your destination Vercel scope to GitLab; GitHub or Bitbucket connections also work. You will now get a regular text field for Environment Variable values, expanding to a multiline field only when a multi-line string is pasted or when you hold shift and press Enter. Projects can now be created from GitLab repositories in subgroups. Build and Development Settings adjustments made during Project creation are retained when the viewport width changes.
When creating a new Project, Team names may now include special characters (such as umlauts), instead of spawning a duplicate Team with a sanitized name. Repeatedly creating a Project from the same Git repository no longer shows loading indicators where framework logos should be in the Root Directory selection, and errors no longer persist between attempts. Updating Git Integration configuration no longer presents an empty confirmation toast. If you are the last confirmed Team Member, you can no longer leave the Team; instead, you are prompted to delete it. Public Deployments viewed by non-owners no longer expose redeploy or delete buttons. When the Dashboard captures a Deployment screenshot, it now identifies itself with a custom user agent so you can filter those requests out of analytics. The account deletion confirmation message now reflects the new 4-day buffer period.
Domains and DNS Handling
The "Name" column for CNAME and A DNS Record suggestions on the Domains page is now more descriptive. If a Domain is configured with a CNAME or A record but also has a conflicting CAA or AAAA record, a helpful note appears on that entry.
Git Integrations and Pull Requests
When a Deployment created by a Git Integration fails or is canceled, the corresponding Pull Request comment now reflects that final state. Pull Requests augmented by Git Integration no longer display "In Progress" for both the "Inspect" and "Preview" URLs simultaneously.
CLI and Platform Changes
Domain-related commands now behave consistently with the Dashboard. File uploads for Deployments reuse existing connections rather than opening many new ones. All ZEIT Now 1.0 features are gone from Vercel CLI. If you run vercel dev in a directory not yet linked to a Project, the CLI now offers to link it automatically. A new vercel link command explicitly handles linking a local directory to a Project. The Development Command from vercel dev again receives an x-vercel-deployment-url header with each request. The upgrade recommendation message no longer appears when your CLI is current.
Docs, Tokens, and npm
All documentation referencing ZEIT Now 1.0 has been removed. Tokens now expire after ten days of inactivity. Vercel-owned npm packages with names beginning in now- or @now are all marked as deprecated.
