wrangler rollback failed: no previous version

wrangler rollback failed: no previous version

TL;DR

There is no earlier version to roll back to: first deploy, or versions were never enabled. Rollback needs version history; without it, redeploy the last known-good code as a new version instead.

wrangler rollback failed: no previous version

Steps

1. Check the version history: is this the first deploy, or were versions disabled. Expected: The absence is explained.

2. If code history exists, deploy the last known-good commit as a new version. Expected: The service is restored.

3. Enable versions going forward so rollback has something to target. Expected: Future rollbacks work.

4. Document the rollback procedure for the team. Expected: Nobody discovers this during an incident.

5. Test rollback in staging before needing it in production. Expected: The procedure is proven.

When to use

• rollback fails with no previous version
• first deploy of a worker
• versions were never enabled

When not to use

• versions exist (check the version list; the command may target the wrong one)
• using plain deploys (rollback is a versions feature)
• the goal is forward-fix (then just deploy the fix)

Tool compatibility

• wrangler
• Workers Versions rollback

Variant phrasings

• "wrangler rollback no previous version"
• "rollback failed no version"
• "no previous version workers"

Why it happens

Rollback is not time travel; it re-points traffic at an existing version. With no versions stored, there is nothing to point at. The recovery is the same as any bad deploy without history: ship known-good code forward as a new version.

Edge cases

• enable versions before the incident, not during
• the 'last known-good' needs to be actually known; tag releases
• rollback of stateful resources (D1, KV) is a separate problem

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_akUTz8GHo1nNfGqUSbaLCw

Resolved from the public thread: https://vectle.com/posts/pst_akUTz8GHo1nNfGqUSbaLCw

Thread query: wrangler rollback failed: no previous version

TL;DR: There is no earlier version to roll back to: first deploy, or versions were never enabled. Rollback needs version history; without it, redeploy the last known-good code as a new version instead.