Platform & Dashboard Updates
The September update brings several quality-of-life improvements to the Vercel dashboard. A new "Login Connections" page in Personal Account Settings replaces the old "OAuth" page and now displays all three Git providers—GitHub, GitLab, and Bitbucket—instead of only GitHub.
In the Project View, clicking a connected Git repository's name now takes you directly to that repository, bypassing the Project Settings page you'd previously land on. For users entering the Project Creation Flow via a Deploy Button, a dedicated screen now explains what Vercel is and can optionally show a preview of the Git repository being deployed.
Several deployment-related dashboard issues were also addressed. The "Visit" button on the Deployment View now correctly suggests the Production Branch when no Production Deployment exists yet, and the "Redeploy" button is always visible for failed deployments, regardless of whether the deployment came from Git. Queued deployments now accurately show that they're waiting for the build to start rather than finish. When a deployment is automatically canceled by the Ignored Build Step feature, a clear message appears on the Deployment View, as it does when a Serverless Function exceeds the maximum unzipped Lambda size.
A guard has been added to prevent redeploying a Production Deployment if a more recent one exists. This ensures older source code can't accidentally overwrite the latest production version; only an explicit "Promote to Production" action will do that. The confirmation modals for "Redeploy" and "Promote to Production" now reliably display correct information, and clicking the latter triggers helpful notifications in the bottom-right corner.
Other dashboard refinements include: the Project Creation Flow pages now stay anchored to the top of the viewport as they grow in height, the "Back" button in the flow works reliably, and switching between Personal Accounts or Teams transitions smoothly from any page. Losing internet connectivity no longer crashes the dashboard—it shows a notification instead. Build logs are automatically truncated at 2,000 lines with a helpful message to prevent browser memory issues, and creating a deployment on a small viewport (phone or tablet) now correctly renders build logs. The Environment Variables removal button in the Project Creation Flow also works again, and a stale banner about Environment Variables being moved to a dedicated page has been removed.
Deployments
Unsupported ranges in the Range request header now return a helpful error instead of a generic "Internal Server Error." The functions property in vercel.json now works reliably with Next.js Serverless Functions inside pages/api. When used with Next.js, unsupported sub-properties trigger a warning message. The 404 page for missing paths on a deployment no longer shows a banner advertising that the domain is available. Clicking the Vercel logo on a public deployment now routes to the current user's dashboard rather than the deployment owner's.
Git Integrations
All three Git integrations (GitHub, GitLab, and Bitbucket) have been rebuilt from the ground up for maximum reliability across the Git workflow. Redeploying or promoting to Production now updates the associated commit status on the Git provider. Pull request deployments from forks that require Team Member authorization (because they'll use Secrets) now leave a comment on the pull request. The PR comment no longer shows "In Progress" for completed deployments.
Deploy Hooks have been scoped to only trigger deployments for the project they're configured on, rather than every project connected to the repository. If a hook creates a deployment but a newer one from the same hook exists, the older one is automatically canceled. When the Ignored Build Step cancels a deployment, the Git integration now reports a clear message as the commit status. Requesting Team access after pushing a commit is now 1.5 seconds faster thanks to the removal of an artificial delay. Installing a Git integration now forwards users to vercel.com instead of the legacy zeit.co domain.
CLI & Documentation
The vercel dev command no longer fails when the tsconfig.json contains comments, which is common when it's generated by tsc --init.
Documentation for the Deploy Button now allows query string parameters in URL fields and includes new "Demo" sections on displaying a Git repository preview in the Project Creation Flow. New docs cover Build Cache, Build Image, and Concurrent Builds. The routes property documentation now points users toward the newer rewrites, redirects, headers, cleanUrls, and trailingSlash properties. The functions property docs clarify which sub-properties work with Next.js. The docs repository has been moved to an internal location for a better engineering workflow, and a new Login Connections page was added under the Platform category.
Other Fixes
A new Entity component in the design system provides a clean way to render item lists. Deleting a Team during its trial period no longer triggers failed-payment emails to its owners. Accounts identified as potentially malicious must now verify their phone number via SMS at signup. A billing bug that prevented some Teams from receiving Git notifications about adding commit authors has been fixed. Deleted Personal Accounts are now reliably pruned after the 4-day recovery period, and the corresponding confirmation email correctly references the 4-day window instead of the previous 48 hours.
