Turbo build machines can now be enabled per deployment
You can now opt into Turbo build machines on a per-deployment basis via Git commit message, CLI flag, or REST API, allowing you to temporarily increase build resources without modifying project settings.
You can now opt into Turbo build machines on any individual deployment. This is useful when you need to increase resources temporarily without changing project settings. You can do this in three ways:
Learn more in the .managing builds documentation
Include in your Git commit message before pushing to GitHub
#VERCEL_BUILD_MACHINE=TURBOUse (Vercel CLI 59.20.0 or later)
vc deploy --turboSet to when creating a deployment with
buildMachineturbothe REST API
Source: original entry ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
Gemini 4 Argon now available on AI Gateway
Google's Gemini 4 Argon model is now available through Vercel's AI Gateway with support for coding, agentic work, and complex reasoning tasks. The model features a 1M token context window, multimodal input capabilities (text, image, PDF, video), tool calling, and configurable thinking levels for enhanced performance.
MAI-Image-2.6 and MAI-Image-2.6-Flash now available on AI Gateway
Microsoft's MAI-Image-2.6 and MAI-Image-2.6-Flash models are now available on AI Gateway, enabling image generation and editing through a single API key without requiring separate provider accounts. Both models support photorealistic imagery, text rendering, targeted edits, and up to five reference images with output sizes up to 1536×1536.
Repository checkout and Git LFS downloads are now faster
Repository checkout and Git LFS downloads are now faster on Vercel, reducing build preparation time. Average checkout time improved by 20%, with LFS-enabled projects seeing a 54% improvement and saving approximately 13 seconds per deployment.