Turbo build machines can now be enabled per deployment
Source
vercel.com
Author
Mehul Kar
Date
Context
Vercel now lets teams opt into a faster 'Turbo' build machine for one deployment at a time rather than changing project-wide settings (vercel.com). It can be triggered by including #VERCEL_BUILD_MACHINE=TURBO in a Git commit message before pushing, by running vc deploy --turbo with Vercel CLI 59.20.0 or later, or by setting buildMachine to turbo through the REST API when creating a deployment. That gives a team temporarily more build resources for something like a hotfix or a launch, without a permanent configuration change.
Key takeaways · AI-distilled
Vercel now lets Turbo build machines be enabled on a single deployment instead of requiring a project-wide setting change, useful for temporarily boosting build resources for one push.
One way to opt a deployment into Turbo build machines is tagging the git commit message with #VERCEL_BUILD_MACHINE=TURBO before pushing to GitHub.
The Vercel CLI supports the same opt-in via 'vc deploy --turbo', but only on CLI version 59.20.0 or later.
Developers automating deploys through the REST API can request a Turbo build machine per deployment by setting the buildMachine field to turbo when creating it.
