Versions & deployments
Every time you change your Worker's code or configuration, Workers creates a version. A deployment determines which version(s) are actively serving traffic.
A version captures the complete state of your Worker at a point in time: its bundled code, static assets, bindings, and compatibility settings. Each version has a unique ID and tracks who created it, when, and from where.
You can optionally attach a message and tag to a version when you upload it.
A deployment determines which version(s) of your Worker are actively serving traffic. A deployment can reference one version (serving 100% of traffic) or two versions (with traffic split between them during a gradual deployment).
Each deployment tracks who created it, when, and which version(s) it includes.
By default, these two concepts are coupled together - when you run wrangler deploy, Workers creates a new version and immediately deploys it to 100% of traffic in a single step.
You can decouple them so that uploading a version and deploying it are independent actions. This gives you control over when new code goes live, and lets you use strategies like gradual deployments or manual promotion. Refer to Deployment management for details.
Wrangler allows you to view the 100 most recent versions and deployments. Refer to the versions list and deployments list documentation for the commands.
-
In the Cloudflare dashboard, go to the Workers & Pages page.
Go to Workers & Pages -
Select your Worker > Deployments.
- Deployment management - Upload versions without deploying them and control when they go live
- Preview URLs - Test new versions before deploying them to production
- Gradual deployments - Split traffic between two versions using percentage-based routing
- Version affinity - Consistently route users to the same version across page loads during a gradual deployment
- Version overrides - Send a request to a specific version by ID for smoke testing and pinning between Workers
- Rollbacks - Revert to a previously deployed version