Vercel CLI can now set new projects to expire
Vercel CLI now allows automatic expiration of newly deployed projects, streamlining cleanup for prototypes and demos with preset durations.
Vercel CLI users can now set new projects to expire automatically after deployment, eliminating manual cleanup for prototypes, demos, and test applications. Supported expiration durations include one hour, one day, one week, two weeks, and 30 days. The CLI displays the exact expiration date and time for each project upon deployment. This feature is activated exclusively when using the vercel deploy command to create a new project.
The expiration setting does not affect existing projects; deploying to an existing project with the flag triggers a warning and retains the current expiration schedule. The CLI prints a clear message when an existing project is updated without altering its expiration. Users must update Vercel CLI to version 65.12.0 or later to access this functionality. The update is available immediately for all CLI users.
The expiration feature is designed to reduce manual maintenance for temporary projects by enforcing automatic deletion after the set duration. The CLI provides immediate feedback by displaying the expiration date and time in the deployment output. This approach ensures temporary projects do not clutter the deployment environment indefinitely. The feature aligns with Vercel’s focus on simplifying project lifecycle management for developers.
To implement the feature, users need only update their Vercel CLI to the latest version and use the vercel deploy command with the expiration flag. The documentation for vercel deploy includes detailed instructions on configuring expiration settings. This update reflects Vercel’s ongoing efforts to enhance developer productivity by automating routine cleanup tasks.