#DeployMents

The Deployment View, Deployment List, and project Domain List now show the Environment of each Deployment and Domain.

As of today, new Deployments using Python Serverless Functions will use version 3.9 and the legacy version 3.6 is being deprecated.

We've updated the design of the comments Vercel posts on pull requests when it creates Preview Deployments for GitHub, GitLab, and Bitbucket.

Find your essential deployments instantly with status and branch filters. From the deployments tab, you can search for branches matching deployments you're interested in.

The Axiom integration enables you to monitor the health and performance of your Vercel deployments by ingesting all your request, function, and web vitals data.

Following the release of Python 3.9, Vercel is deprecating support for Python 3.6 which reached end of life last year.

Vercel now supports pnpm v7 and automatically uses it for install and build commands when your pnpm-lock.yaml has version 5.4.

You can now use a total of 64KB in Environment Variables for each deployment on Vercel, enough for large authentication tokens, JWTs, or certificates.

You can now make Preview Deployments private for free on all plans, with Vercel Authentication for team members and shareable links for collaborators.

Comments on Vercel Preview Deployments are now generally available giving you a centralized review workflow for rapid iteration.

You can now filter deployments by environment type as well as by branch, making it easier to find production and preview deployments.

The Active Branches view for Deployments has an updated design which is now filtered on open branches with deployments.

You can now redeploy or promote any deployment to production from the Vercel dashboard, whether it was created with the CLI or the Git integration.

Azure DevOps customers can now use the Vercel extension from the Visual Studio Marketplace to trigger deployments on every commit or pull request.

Enterprise customers are now able to configure builds of their Production deployments to begin before any builds of their Preview deployments.

Ensure your past production deployments remain secure by enabling Standard Protection as the default setting for your deployments.

Trusted IPs are a feature of Deployment Protection that allow you to limit access to your deployments by IP address.

Deployment Protection is now enabled by default for all new projects, and our full set of protection options is now generally available.

Ruby v3.2 is now generally available and is the new default runtime version for Ruby Builds and Serverless Functions.

You can now initiate new deployments directly from the dashboard using a git reference. This approach is helpful when git providers have service interruptions with webhook delivery.