Migrate from v1 to v2

Acme Cloud v2 brings faster builds, scoped API keys and preview environments for every pull request. Most teams finish the move in under an hour.

What changed#

Area	v1	v2
CLI deploy command	acme push	acme deploy
Authentication	Personal tokens	Scoped API keys
Previews	Manual	Every pull request
Build cache	Per branch	Shared across branches

Migration checklist#

1. Install the v2 CLI on your machine and in CI.
2. Create scoped API keys and replace legacy tokens in your CI secrets.
3. Rename acme push to acme deploy in your scripts.
4. Turn on Settings → Workspace → Use v2 builds.
5. Deploy once to staging and compare the result.

Rolling back#

Until December 31, 2026 you can switch a workspace back to v1 builds from the same setting. Deployments made with v2 stay online.