The Vercel dashboard lets you manage all your current and previous deployments. To manage a deployment, go to your project from the Vercel dashboard. Then click the Deployments tab from the top navigation.
Vercel CLI and Vercel REST API also provide alternative ways to manage your deployments. You can find a full list of the commands available in the Vercel CLI Reference, along with the deployments section of the Vercel REST API Reference.
You can filter your deployments based on branch, status, and deployment environment. Navigate to the Deployments tab inside your Project dashboard and select an option in the All Environments or Status dropdowns.
The dropdown for Status filters the deployments according to the deployment status.
The Deployments tab with the status filter dropdown open.
Valid status values include:
- Ready: A successful deployment
- Error: An unsuccessful or failed deployment
- Building: A deployment currently being built
- Queued: A deployment waiting to be built
- Canceled: A deployment that was canceled
The drop-down for All Environments allows you to filter the deployments according to the environment, including Production and Preview.
The Deployments tab with the environments filter dropdown open.
The dropdown search menu for branches allows you to filter and select any deployment by branch name.
When you update your Project, Vercel automatically redeploys your application to integrate new and existing changes. You update an application by editing, adding, or deleting its contents.
However, there can be situations (e.g. bad cached data) where you need to Redeploy your application to fix issues manually. This section contains information about how and when you need to redeploy your application to Vercel.
The Deployments tab lists all the previously deployed builds. Click the vertical ellipsis (⋮) icon where you will find the option to Redeploy that specific build once again.
This takes you to a popup window that prompts a Redeploy message. To surface the default behavior and provide granular control, you can now find an option for including the Build Cache when redeploying an existing Deployment.
Option to confirm redeploy to production.
Other than your custom needs to redeploy, it's always recommended to redeploy your application to Vercel for the following use cases:
- Enabling the Analytics
- Changing the Environment Variables
- Outage Resiliency
- Making changes to Build & Development Settings
- Redirect or Rewrites from a subdomain to a subpath
There may be times when you need to promote an existing preview deployment to production. For example, if you need to roll back the code served to your visitors to a previous version without changing the source code or if you are in a situation where you need to use a branch that isn't set as the Production branch temporarily.
The Deployments tab lists all the previously deployed builds. Click the vertical ellipsis (⋮) icon where you will find the option to Promote to Production that specific build.
This takes you to a popup window that prompts a Promote to Production message which will include the domain(s) that will be linked to the build once confirmed. Please note that if you have different Environment Variables set for preview and production deployments then the variables used will change from preview to those you have linked to the Production environment.
Option to confirm promote to production.
- The deployment will be rebuilt using Production domains and environment variables, you cannot use your Preview environment variables in a Production deployment
As an alternative to promoting a deployment to production, you may instead want to quickly revert to an earlier deployment. This is made possible through Instant Rollback. For more information on how and when to use it, see the Instant Rollback docs.
If you no longer need a specific deployment of your app, you can delete it from your project. Click the vertical ellipsis for the deployment you want to delete from the Deployments tab. Then click the Inspect Deployment option, which directs you to the details of that deployment.
From here, you can Delete the deployment. Deleting a deployment prevents you from instant reverting and might break the links used in integrations, such as the ones in the pull requests of your Git provider.
Was this helpful?