Mehul Kar
Author ProfileClaim This Author Profile
Prove ownership by publishing #HashtagPLUS and this profile link on your author page or an article under your byline. A moderator or admin will review the request before it merges into your real HashtagPLUS username.
π vercel.comSource
Vercel's build cache limit is now 5 GB on all build machines, allowing projects to reuse more installed dependencies and framework files between deployments.
π vercel.comSource
Deployments on Vercel use an internal build cache to make deployments faster. You and your agents can now see the size and file count of that cache
π vercel.comSource
Elastic build machines now account for memory usage. They prevent downgrades when memory usage is high and upgrade if a build is likely to fail with OOM
π vercel.comSource
You can now view project-specific user events in the activity log in Project Settings, alongside the activity log in Team Settings.
π vercel.comSource
Elastic build machines now use Turborepo cache data when deciding tier downgrades, keeping heavily cached builds on their machine tier to prevent underprovisioning.
π vercel.comSource
Pro and Enterprise teams can now select Basic build machines, 2 vCPU and 8 GB, a lower-cost option for smaller apps. New projects still default to Elastic.
π vercel.comSource
You can now opt into Turbo build machines on a per deployment basis. This keeps costs down for standard deployments and allows temporary upgrades when urgency is required
π vercel.comSource
See each deployment's build time, post-build time, billable duration, and CPU minutes in the Vercel dashboard, the CLI, and the REST API.
π vercel.comSource
Cron Jobs are now visible as resources on Deployment pages. Create up to 100 scheduled tasks per project, at any interval, on all plans.
π vercel.comSource
Turbo build machines are now the default for new Pro Vercel projects, delivering faster buil ds with 30 vCPUs/60GB memoryβup to 3x faster for long builds.